Scenario:

You have form validation on a textbox called "SearchString" for the form id "blah".

Form id "blah2", which is on the same page, also has a textbox called "SearchString", because they basically submit to the same page (for our purposes, these two forms need to co-exist).

If you enter data into form ID "blah"'s SearchString textbox and hit SUBMIT, ASP.NET's form validation kicks in and tells you that you need to complete the form.

WHY? Because it is erroneously regarding two textboxes from two different forms as being the same textbox.

Why can't it differentiate between blah.SearchString vs. blah2.SearchString?

Hi there,

The thing is, ASP.NET is build around the concept of one single form. This means it considers all unique controls (with an ID attribute) as part of the entire form.

To solve this problem you can disable the validations off the controls on the form you are not submitting.

For a good start on this subject, check here:

http://www.aspalliance.com/kenc/faq6.aspx

HtH

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

Thanks...if this is by design then I can't help but regard it as counter-intuitive. It is not realistic to expect a page to only ever have one form. I suppose I can disable the validation, but then I'd have zero validation for either form which, again, seems counter-intuitive.

I find it puzzling that in the straight HTML world, values from form id "A" are differentiated from form id "B" with no problem. But now with asp.net, it seems to ignore the form id altogether, lumping two textboxes that come from two different (and more importantly, independently named and id'd) forms as being the same textbox just because they share the same name.

Unless I'm missing something, the object-oriented world should have no problem differentiating between myFormOne.SearchString vs. myFormTwo.SearchString.

Hi there,

This is not quite true. You can disable each individual control with client side code. So, in the btnSendForm1_onclick() method (for example) you can disable the validation for form 2 and vice versa.

Hth

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

cacklebunny..!
we have the more then one form on the same page and what is the problem declaring them coz they have their separate ID and a very good thing in ASP.NET that you can code down the button click events of the form control(button).

PEACE