Validation problem in custom control

[ake_krakbar]

Hello folks! I have developed a custom control (upload components, kinda) wich is using a validation component to validate user input. The custom control consists of an upload field, a validation control & a submit button + various logic. If I use one control per aspx there is no problem, but when I use two upload components in one page, sh*t hits the fan. The problem is that when the user fills in data in the first control and push the ok button, validation is triggered - even in the second control. How do I permit the controls from validating each other. If I set the CausesValidation property to false there won´t be any validation at all, and that´s bad...

[thomasa]

You could seperate them by getting the ID from each control, and only validating the control if the ID is coresponding to the button you pushed Hope it helps Thomas

[ake_krakbar]

Hello Thomas! Would I have to perform this test inside the aspx that is using the controls or could I do it inside the control (would be better). The problem is that the buttons triggering the events have the same ID (becuase they are just to instances of the same custom control). I´m not quite following you. Could you please fill me in?

[Andy Brummer]

Make sure your control derives from INammingContainer this will give unique ids to your child controls.

[ake_krakbar]

yeah thats true. Forgot about that! :-> But still, this check can´t be performed inside the custom controls, right?

[Andy Brummer]

You should be able to get the conrols operating completely independently on the page.

---

I can imagine the sinking feeling one would have after ordering my book, only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon