> > That's a horrible way to do it. Quite inefficient. > > > > A better route is to check your DB's docs and see how they > > expose the last inserted sequence value. In MySQL it's > > LAST_INSERT_ID(), with MS SQL Server its one of three > > @IDENTITY variables. Run your INSERT, and then select the > > value back out using this mechanism. You may or may > > not need a transaction, depending on the specifics, and you > > definitely won't need CFLOCK. > > That's only reliable inside a transaction. Don't leave that > part out.
Actually, depending on your database, a transaction may not be required just as Barney states. For example, if you're using MS Access, the entire table is locked when you write to it, so a transaction wouldn't be required. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:192412 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
