Hi Jose
This sounds like a logical approach.
Have you looked at the commit/rollback features? (assuming you are
using sql server)
Regards,
Len Wright
Plus International Corp
www.plusinternational.com
Direct: 604-415-2384
Fax:604-415-0830
>>> [EMAIL PROTECTED] 05/21/02 04:02PM >>>
I use a "form lock" user variable.
When submitting forms, I always have a form, a form confirmation page
and
then the actual insert. What I do is set the "Form Lock" user variable
on
the first action to "Start Thingy". The last action before the form
is
inserted/updated is to set the same variable to "Finish". I put the
"formlock" assignment and the insert/update within a condition
statement If
"Form Lock" = "Start Thingy" then ..... This prevents the user from re
inserting stuff by hitting the back button.
I re-use the same user variable over and over to save memory. I always
set
the "Form Lock" to something unique to that taf. I also set the "form
Lock"
always to "finish" when the insert/update is complete.
Is this the most efficient way of doing things? I always reuse the same
user
variable so there is not any memory issues.
What do other people do to prevent the double insert.
Jose
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to
[EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
