Stan, >Thanks for the response. The particular page I am working with is >used to take in registrations for a conference, a given individual >will login and register X number of participants for their group. >>From the primary screen they have the ability to add new registrations >or update existing ones, in each case the forms are identical in >structure. They are all on a single screen for the ease of the user, >and I'm adding the exact same validation rule set to each form. > >Anyhow... I have a hard time believing this is that rare... maybe I'm >just mistaken, but the instance above is one of probably a dozen or so >I can think of in the context of my current project. > >Thanks again for the reply.
I've done things like that in the past and I either used unique field names all in one field (i.e. name_1, name_2, etc.)--which allows you to do all the updates in a single POST operation--or by re-using the same form to add new participants. Anyway, I can see why you're using new <form /> blocks. Using the each() method definitely is a good work around for the issue. However, I've had to use the $.validator reference many times to do extended validation--so having the validator() function return a reference to this far outweighs the benefit to me of being able to attach multiple forms. The each() method provides a really nice way to wrap up that functionality for multiple forms. -Dan
