Re: Witango-Talk: Submitted forms are blank when going 'back'

[Atrix Wolfe]

Ive experienced this same thing Dave.  My solution has been to not rely on the back button.   Might be a pain but you can put an error handling html on the place (s?) they have errors and put a button there that leads back to the form instead of having them use the back button.   You can put the parameters they used in the search as hidden args passing it back to the form and have the form be populated with the values of the args.   that was kinda a mouthful i bet its an earful too :P   heres what i mean.  On the search form set up your inputs like this:   Starting Date: <input type=text name=StartDate value="<@arg StartDate>"><br> Ending Date: <input type=text name=EndDate value="<@arg EndDate>"><br>   and then in your error handling html of the action that is erroring, put something like this (setting the action of the form appropriately to go back to the search form):   <form method=post action=""> <input type=hidden name=StartDate value="<@arg StartDate>"> <input type=hidden name=EndDate value="<@arg EndDate>"> There was an error!<br><br> <input type=submit value="Search Again"> </form>   Another thing to think about is you can use _javascript_ to validate the users input before they ever submit the form so this situation never even has to come up.  Its alot friendlier when you hit submit having a popup window saying "That is not a valid date" then for a user to hit a tango error screen and have to hit the back button (:   I have a _javascript_ utilities file i made which validates/corrects dates and currency and has a couple other little functions, if your interested i could send it to you, let me know   ----- Original Message ----- From: Dave Machin To: [EMAIL PROTECTED] Sent: Thursday, July 31, 2003 9:13 AM Subject: Witango-Talk: Submitted forms are blank when going 'back' Not really a WiTango problem directly, but I have a couple forms that end-users submit to request a graph to be generated by WiTango.  They fill out a variety of information and click submit, which passes the post-args and <@userreferenceargument> back to the same .taf file which then generates a report.  Sometimes if they've left some fields blank and the .taf reports an error message, when they click 'back' the form has reset itself with blank fields.  But sometimes it retains the information the user entered.  Is there some way to force the browser to always retain the original form information? Dave Machin E-Mail.  [EMAIL PROTECTED] Tel.  805.614.0123 x 30 Address:  3130 Skyway Drive #702 Santa Maria, CA 93455 ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf