Validation is testing to determine whether the user entered into the field.
(34 printed pages) Introduction Looking at Validation The Required Field Validator Control The Compare Validator Control The Range Validator Control The Regular Expression Validator Control The Custom Validator Control The Validation Summary Control Conclusion In your studies of ASP.If the data is incorrect or not valid, you can send back a response stating this.If, however, when the user clicks the Submit button, a scripting language that is part of the overall HTML page is initiated to check the validity of the data before it is sent to the server, this is client-side validation.When you used server-side validation with ASP 3.0, if something the user entered was wrong, you could repost the form and ask the user to correct the information in that particular field of the form.Sometimes, you carried the correct input from the other fields back to the form page, and populated the fields for the users so they didn't have to re-enter the same information again.From there, you can compare user input in different fields or against values that might be held in other repositories, such as a database.
You can check for many types of information, as you learn in the rest of this article.
Validation server controls are a series of controls that help you validate the data that the user enters into the other controls that are provided with ASP. They determine whether the form can be processed based upon the rules that you define in the validation server controls.
One of the most common elements of Web pages is a form in which the user can input data that is posted back to the server.
It was a lot easier to understand the difference between these forms of validation when you coded Active Server Pages 3.0 because, as the programmer, you personally performed almost all data validation.
You yourself either programmed it to be client-side or server-side.
Some users are not interested in spending enough time to enter the correct information into a form, and in some cases, users might even intentionally enter false information to gain access or get past a certain step in your application's workflow process.