Questions back at you:
1) Are you concerned with someone who inserts a form and hitting their back button only to get the form again without anything in it or an EXPIRED page?
2) Or are you asking if someone goes into a page where they are updating information, and then hits refresh? Wouldn't it just refresh the page and the data from the db?
Maybe I am missing something on your original post.
Paul Giesenhagen
QuillDesign
----- Original Message -----
From: Jeff Chastain
To: CF-Talk
Sent: Wednesday, July 28, 2004 1:33 PM
Subject: Best Practice - Forms
I have dealt with this in a variety of different ways in the past, I am
wanted to see how other people did it. I have a form. This same form is
reused for creating a new record as well as updating an existing record.
So, the question is how do people 'control' the back button and the case
where the user submits the form, backs up, and resubmits it again? In the
case of a create operation, the first time the form is displayed it would be
empty, but upon reloading the form, it would contain the original data and
would now be an update operation. In the case of an update operation, the
first time the form is displayed, it would contain the current data, but
upon reloading the form, it would contain the updated data and still be an
update operation (would go to an update query instead of an insert).
So, what are your best practices for handling form input and reusing a form?
Thanks
-- Jeff
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
