What database are you using? If it's one that supports "auto" columns or "sequences" (automatically incremented counters, specifically for primary keys), consider using such a function when you insert. If your database doesn't support that, then I'm not sure what you can do.
Well if there is support for transactions in the database you could maintain a table of sequence numbers and increment that as part of the transaction used for the insert.
What I just described is just good database practice. There's probably another way to trap the case of submitting the same form twice.
Could you put mutex protected flags in the session to indicate whether or not the form had been submitted?
Nick
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
