Server-side validation incorporates code validation into a form handler. NET application on the server that provides the functionality that your form needs for processing after a customer has submitted it.
Because the code is stored on the server, server-side validation requires a roundtrip to the server.
For example, if you have a form that populates a drop-down list based on the value of another form field, server-side processing may be needed to pull data from a database and populate the drop-down list.
Client-side validation provides validation within the browser on client computers through Java Script.
(16 printed pages) Introduction Getting Started Writing the Validation Script Connecting the Form to the Script Associating Form Fields with Custom Script Code Listing Conclusion When you create forms, providing form validation is useful to ensure that your customers enter valid and complete data.
For example, you may want to ensure that someone inserts a valid e-mail address into a text box, or perhaps you want to ensure that someone fills in certain fields.
In order to access your form fields in code, you need to assign names to the form and each of the fields. For more information see, NAME Attribute | name Property.
You may assign any name you want that is composed of alphanumeric characters (without spaces), but to make writing the code easiest, you should provide a useful, friendly name for each of the fields.
For more information about HTML and Web scripting, see one or more of the following references.
In addition, each of the fields should have a unique name.
Use the following table to assign names to all of your form elements.
Because the code is stored within the page or within a linked file, it is downloaded into the browser when a user accesses the page and, therefore, doesn't require a roundtrip to the server.
For this reason, client form validation can be faster than server-side validation.
Microsoft® Office Front Page® 2003 allows you to create some custom validation within the form feature.