> The action page has a CFLOCATION to the refresh page. In that case, there is no "action page" from the pov of the browser... just an http redirect header, which the browser doesn't put into the history.
> A combination of the progress bar and the JavaScript code sent out > before should take care of most situations where the user wants to go > back and resubmit (unless anyone else has other nice tricks to share > :-) ). 1) put a hidden field in the form (called "frmSubmitted" or somesuch) and populate it to "N". 2) when the form is submitted, check that the value of this field is "N". If it is, set the value of this field to "Y" and continue with the submission. Otherwise, pop up an alert or use some other method of handling the situation, but do not submit the form. 3) other option: check the value of this field onload of the page, and do something if it is not "N". This way the users don't spend ten minutes editing information only to get slapped in the face with a wet fish when they try to submit the form. The back button is one of the most used browser features - users get a little bent out of shape when you disable it without warning. /t ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224231 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
