Yep, that's one of the methods we tried, but it doesn't work when you're trying to track down a problem lock because the failure actually happens on the opening CFLOCK statement, so any code you put after it to track it doesn't get executed.
It's a tough one. > -----Original Message----- > From: Ryan Guill [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 23, 2006 11:09 AM > To: CF-Talk > Subject: Re: weird locking error > > To track what locks are active, you could put code inside of the lock > that sets an application variable and then removes the set after the > </lock>. Just an idea, but not a good one for a system wide view... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:236088 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
