Once a form is created, it can deposit that information into an appended database, where other statistical applications can massage the data into any structure desired by the final user.

validating the form-85

The alternative to client-side scripting is to validate your data when it is returned to your application.

One downside to this is the added complexity of developing an interface that validates data and displays errors. Most of the added complexity of server-side validation is handled behind-the-scenes by Marmot.

Sometimes it is not sufficient to validate what the data is or is not.

Rather, it must be validated by what it looks like: its pattern.

The information is collected by another person, and along with other forms, compiled (by hand) into a final readable product.

Not very efficient; however, that’s the way it was done, many long years ago.

Today forms are filled out on a computer screen; the data is validated and compiled into a readable final product, along with relevant statistics and averages.

What I’m describing is creating electronic forms, designed, implemented, and finished, all with the help of Adobe Dreamweaver.

Causes any date entered in the specified field to be validated as a valid date (date, time and date/time are supported).