RE: Preventing User from Re-submitting Add Record Form

2002-09-09 Thread Everett, Al
There's a couple of ways to handle that. One is to set a session variable or cookie at the time they reach the confirmation page. The idea being that your form template would check for the existence of that session variable or cookie and, if found, stop them from submitting the form. Another

Re: Preventing User from Re-submitting Add Record Form

2002-09-09 Thread Douglas Brown
What about using a session var on your action page and giving the value of the time that it was when the submittal occured. And then in your form page you could say.. cfif isDefined(session.submittalTime) If you are trying to edit this form, please use the link a href=Click/a cfabort /cfif

RE: Preventing User from Re-submitting Add Record Form

2002-09-09 Thread Phoeun Pha
I first thought that this was an issue with people clicking the submit button twice but it's just another case of THINGS YOU CAN'T CONTROL. Here is something you can do. On that add new member page, write a javascript to clear all the fields, you know, when the page loads (ex. use onload

RE: Preventing User from Re-submitting Add Record Form

2002-09-09 Thread Tony Carcieri
[mailto:[EMAIL PROTECTED]] Sent: Monday, September 09, 2002 4:46 PM To: CF-Talk Subject: RE: Preventing User from Re-submitting Add Record Form There's a couple of ways to handle that. One is to set a session variable or cookie at the time they reach the confirmation page. The idea being that your

Re: Preventing User from Re-submitting Add Record Form

2002-09-09 Thread Douglas Brown
PROTECTED] Sent: Monday, September 09, 2002 1:49 PM Subject: RE: Preventing User from Re-submitting Add Record Form couldn't you use recordcount? cfif #somevalue.recordcount GT 1 !---go back a page or some other piece of code--- cfelse !---do something else--- /cfif i know in ASP

Re: Preventing User from Re-submitting Add Record Form

2002-09-09 Thread Matt Robertson
I set a hidden unique form var, then once the form is submitted convert that submitted unique value to a client var. Subsequent submission attempts compare the current form UID to the stored, submitted form UID(s) and bounce the submission if a dupe is found. I rely on client vars for