David said: "....I would write the main database row for the customer and then retrieve a unique customer id and hold that as a session variable."
This sounds like what I would like to do. Can you point me in the direction of some information/code to implement this approach? What happens if a user bails out half way through the application process? Can you detect if the session "expires" then you delete the records from the database for that row? Or can they return later? I have added a "complete" flag to the database to indicate a completed application, so perhaps I could utilise this?
I cheat on this, in a multi user environment. I write out one column as the session variable and then retrieve the row based on this rather than an ID. I am not convinced that @@Identity works if there is more than one user.
After you have collected and written all the data, you can set the column with the session variable to Null. (Or just leave it if you've indexed it.)
It's not ideal, but it works if you're using SQL DDL in ASP.
Regards, David
____ � The WDVL Discussion List from WDVL.COM � ____
To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] Send Your Posts To: [EMAIL PROTECTED]
To set a personal password send an email to [EMAIL PROTECTED] with the words: "set WDVLTALK pw=yourpassword" in the body of the email.
To change subscription settings to the wdvltalk digest version:
http://wdvl.internet.com/WDVL/Forum/#sub
________________ http://www.wdvl.com _______________________
You are currently subscribed to wdvltalk as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
