variable, but storing the record ID might be simpler. I will have to think
about this one some more.
Thanks for all of the feedback.
-- Jeff
Quoting "Tangorre, Michael" <[EMAIL PROTECTED]>:
> Right after your initial insert set a session variable containing the some
> kind of ID to the record. Before you do another insert, check to see if the
> session var exists and if so, use an update query instead with the ID in the
> var...
>
> Mike
>
> > The problem I have run into in the past is that a user will
> > submit a form, then see the results (confirmation page) and
> > need to make a change, hit the back button, and end up
> > creating record #2 instead of updating the original record.
> >
> > So, in this case, how do you make the second pass on the form
> > actual perform an update operation instead of an insert?
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
