IIRC what you have written will only give you rollback capability, which isn't your problem. If you set the isolation to "serializable" you will do the following (from the -- ahem -- manual):
"...places an exclusive lock on every data table in use for the duration of the transaction. Causes access to the database to be single-threaded and is therefore not recommended for normal database access." Nor does it affect the cfsets you have in there. You want to use a named cflock to single-thread these different processes like you are trying to do. Also you don't need your second query. Initialize the values once and only once at application inception via a single query. Then update the vars directly until the next reset. But far better still: Do Not create a 1-row db like you have. Put in a "date registered" field in your registration db. When the application initializes, count the number of entries that were registered "today" and total count. Make these results your app var. Increment the app vars directly from there. This keeps you from gagging your app with either a cftransaction- or cflock-based chokehold. -- [EMAIL PROTECTED] Janitor, The Robertson Team mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJP Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:272606 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
