although I don't use the cf_reuseform tag, the issue of non-JavaScript form
validation is one that affects most folks...
The way I handle the issue is this:
User visits form page
Form field value defaults are determined by checking the values within
db-based client variables (or you could use good ol' session variables)
User submits form.
Form results are stored in db-based client variables (or you could use good
ol' session variables), the same ones mentioned earlier
Form validation routine is executed
If form results are rejected, a CFLOCATION is done back to index.cfm, with
the fuseaction being the one that invoked the form page in the first place.
Since the db-based client variables are now populated with values, these are
loaded up into the form, thus preserving the user's original submission.
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
> -----Original Message-----
> From: Daniel Lancelot [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, January 12, 2001 2:51 AM
> To: Fusebox
> Subject: RE: Form Validation cf_reuseform
>
> Hi Ed,
>
> I asked a similar question a couple of months back, and had 1 vague
> reply...
>
> {redacted}
>
> Any problems let me know (or if anyone thinks this is not the best way of
> soing it, i'd be interested too...)
> {redacted}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
