Paul, The simple rule of thumb is that if you are using application, session or server variables then you need to lock them on reads and writes. Meaning if you have a variable called Application.DSN, then you need to lock it when you write it and also lock it when you read it.
If your application does not use application, session or server variables, then you don't have to worry about it. See Nate Weiss' talk at DevCon on locking for more information: http://www.nateweiss.com Good luck, Beau -----Original Message----- From: Paul Ihrig [mailto:[EMAIL PROTECTED]] Sent: Monday, November 12, 2001 9:25 AM To: CF-Talk Subject: i don't understand cflock? can you explain it? in the WACK 4.0 & AID book's there is only a 1/2 page or so related to it. in mastering cf 4.0 there are a few pages about it, that i really don't understand. if i am not using application variables, just calling data sources for drop down list as well as calling data source for update pages, should i use cflock? you know just your standard generic forms, which is about 80% of my daily work here. how can i get a good grasp of WHY to use them? Thanks in advance. any advice would be great! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com 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
