If the name of the query is application.queryname (for example), then yes, it must be locked.
But rather than locking the entire query - to save time name the query request.queryname (for example) then after the query move the var into the application scope. Anytime an application, server, or session variable is in code it's either a read or a write, and must be locked. Chris Norloff ---------- Original Message ---------------------------------- from: "Andy Ousterhout" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] date: Sun, 5 May 2002 14:20:09 -0500 >Should I put named locks around database queries or should the database >engine (Access2000)? I have heard the Access sometimes has indexing issues >and I was curious if anyone out their had experience with locks reducing the >likelihood of an indexing issue. > >Thanks, >Andy > > ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
