I'll be interested in hearing answers from "wiser" list members, but my feeling was that 99% of the time tables using an auto-number also had a unique field elsewhere. So indeed my strategy has always been to do exactly what you say. If this alternate unique tuple exists, then you don't even have to worry about race conditions. If you do *not* have any unique set of fields in the table, then I suppose you are stuck relying on hoping to avoid race conditions.
Just my two cents. Paul > -----Original Message----- > From: Joshua Caesar [mailto:[EMAIL PROTECTED] > Sent: Friday, March 14, 2003 1:40 AM > To: [EMAIL PROTECTED] > Subject: Retrieving autonumber after insert > > > Is there a general DBI call , or DBD::ODBC call, to retrieve the > autonumber generated after an insert ? > Or is my best bet to do the insert, then do a select for the id, using > the inserted values in a where clause, and depend on the fact that there > hopefully shouldn't be race conditions on an app that will be for one > user only 99% of it's life. > > I am 150 miles away from most of my documentation, so please excuse me > if this is something easily looked up. > I am using Perl 5.6.1 built for cygwin-multi, DBI 1.30, and DBD::ODBC > 1.01 against an Access 2000 database. > > Thanks in advance, > > Josh Caesar > [EMAIL PROTECTED] >
