> :-) well from a database point of view you are wanting to do > one of two things.....[a] stop the offending process > happening BEFORE it gets to the SQL Server or [b] allow the > process to commit but to be setup in the queue on the SQL side....
I know. > variety of angles. My guess would be to put in cflocks > around the insert queries which, would obviously stop any > deadlock on the CF and then in turn the SQL > side. I've done that - doesn't work. This is because the lock is only performed for the current request - not multiple concurrent requests across the application from other users. You can tell I'm sleepy because of the next question I'm about to ask - can I somehow use shared scope locks to tell a concurrent request to wait? You could the obivously do cftransaction as well, but > I cant see > where that would help in this situation as all you want to do > its "queue" requests up. What's what I said. -- ** 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]
