If you're using SQL server, I would check @@IDENTITY or @@ROWCOUNT. The 1st contains the value of the newly created row, the 2nd one contains the number of rows modified/created. michael -----Original Message----- From: David.Cantrell at Gunter.AF.mil [mailto:David.Cantrell at Gunter.AF.mil] Sent: Tuesday, August 20, 2002 9:34 AM To: thelist at lists.evolt.org Subject: RE: [thelist] ASP/VBSCRIPT: best way to verify successful record insertion >yes. that is exactly what i'm talking about. the problem i was running >into though was that of uniquely indentifying the registrant. that's why >i had the idea of the session variable. Chris, What DBMS are you using? Access and SQL Server both support automatically-generated IDs. Just create a new field in the table with an auto-number or auto-id and set it as the primary key, and you are guaranteed that no two records will be "identical" as far as the DBMS is concerned, even though they may have the exact same information byte-for-byte. I had a bookmark to a really great SQL/DBMS intro, but it's gone now. Found these lists at google, maybe they'll help you: DB: http://www.tutorgig.com/showurls.jsp?group=1349&index=0 SQL: http://www.tutorgig.com/showurls.jsp?group=118&index=0 -dave -- For unsubscribe and other options, including the Tip Harvester and archive of thelist go to: http://lists.evolt.org Workers of the Web, evolt !