required field validators -- grouping??

[matt]

i have a webform that offers users two options: username & password, or
a bunch of "new user" signup textboxes. if they signup, many fields are
required. there is one button for each group ("Login", or "Sign Up").

however, im noticing that having required fields on the new user area
is a problem -- if a user tries the top option (login: username &
password) and hits the "Sign Up" button, that the lower (new user)
fields lite up as "Required"...! obviously, this is not my intent.

is there no simple .GroupName property for the required field controls
-- you know, so that one group's button doesnt trigger the failure on
another set of items? seems like a no-brainer to me.


thanks,
matt

 

[matt]

however, im noticing that having required fields on the new user area

is a problem -- if a user tries the top option (login: username &
password) and hits the "Sign Up" button

^^^^^^^^^
typo -- should be "Login" button. it inadvertantly triggers all the new
user validators.

thanks, ill check your product out.

as for .NET 2.0, if they have a groupname for the button and then the
validators, i would think that would take care of my problems.


matt