The Validators in ASP.NET 1.x were written using DHTML, a system specific to
IE and IE/Mac browsers. They simply do not provide client-side validation on
other browsers. ASP.NET 2.0 resolves this. So does my Professional
Validation And More,
http://www.peterblum.com/vam/home.aspx, which greatly
improves all aspects of validation and data entry on web forms.
CustomValidators should always have a server side evaluation function. It
should be called by Page.Validate() unless you forget to hook it up or the
Validator is Enabled=false or Visible=false.
Additionally, if you use the ControlToValidate property, it will not be
called when the associated field has a blank value. If you need to support
blank values, do not assign ControlToValidate and make your evaluation
function refer to the control directly instead of using the value in the
Args parameter.
--- Peter Blum
www.PeterBlum.com
Email:
PL****@PeterBlum.com
Creator of "Professional Validation And More" at
http://www.peterblum.com/vam/home.aspx
"Jason" <Ja***@discussions.microsoft.com> wrote in message
news:6A**********************************@microsof t.com...
I am able fire my field validators in FireFox on the server side using...
Page.Validate()
If Not Page.IsValid Then
Exit Sub
End If
But the it won't fire Custom Validators. Anybody know why?
