> Like Adrian says, there is the possiblity for another transaction to sneak in > between your first query and the select max... CFTRANSACTION causes > anything inbetween to be treated as an atomic Db transaction thus ensuring > that the select max... is pulling out the record that was created as a result of > the insert in the same transaction block.
Oh, I thought (perhaps wrongly) Neil was saying that Access's own locking mechanism wasn't good enough to prevent an insert followed by a select MaxId, wrapped in a cftransaction, from allowing another insert query to creep in between. However, if it is, then -- yeah, to hell with the named lock and just use cftransaction. -- Aidan Whitehall <mailto:[EMAIL PROTECTED]> Macromedia ColdFusion Developer Fairbanks Environmental Ltd +44 (0)1695 51775 Queen's Awards Winner 2003 <http://www.fairbanks.co.uk/go/awards> ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________ -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
