1. Other than locking the DB... why are you trying to lock it? (i.e. ... the web is stateless, so the CF Lock would only function to lock a transaction occuring during this request.)
2. If you are trying to run a sql command that takes longer than a standard request... why aren't you doing that from inside your sql server? (and with that... what SQL server are you using? ... is this a internal server... or rented shared server online?) 3. If this is a CMS type check in check out lock, then you could do a combination of (with msSQL... not in access) locking the transaction to make sure only one person can do this at a time, having it create a GUID key to show it is locked, and to check it back it, and when the user gets done... or when your application says he had it checked out to long if you want that... log it checked back in. Heh... that is a quick (not carefully worded) overview of what it sounds like you need. John Farrar ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
