:wave:
I'm new to this asp.net stuff. My dev lead and I are both trying to learn how to do this. He built some pages and asked me to add the validation controls to them.
The first page has a series of text boxes with autopostback = true. I can put CompareValidators onto the form and assign them to the textboxes, and they seem to work right.
On my second page, however, the controls are being built on the server using vb code. The CompareValidators seem to work on the client side. On the server side, however, the CompareValidators always have an IsValid property = true, even when the value of the textbox clearly violates the conditions. I've checked all the properties I can think of and I can't see any difference between these dynamically generated validators and the static ones I have on the first page, so I'm thinking there must be something else going on.
Let me know if you need any more info or have any ideas.
I'm new to this asp.net stuff. My dev lead and I are both trying to learn how to do this. He built some pages and asked me to add the validation controls to them.
The first page has a series of text boxes with autopostback = true. I can put CompareValidators onto the form and assign them to the textboxes, and they seem to work right.
On my second page, however, the controls are being built on the server using vb code. The CompareValidators seem to work on the client side. On the server side, however, the CompareValidators always have an IsValid property = true, even when the value of the textbox clearly violates the conditions. I've checked all the properties I can think of and I can't see any difference between these dynamically generated validators and the static ones I have on the first page, so I'm thinking there must be something else going on.
Let me know if you need any more info or have any ideas.