>>I assume that users want to look at the record, make changes and save without having to worry about any other user doing the same thing to the same record at the same time.
Depends what you call "user", I would rather say "developer" here. For me, the user is the one who uses the applications I develop. I'm the one who "wants to lock", the users have difficulties to make the difference between a computer and a toaster ;-) But yes, this is what I want, and this is only basic practice in all multiuser database applications. I've been always amazed by the futility of the CFLOCK tag. For me, it should lock records or tables, not just variable scopes which the CF server should be able to manage automatically. By the way, this is exactly what it has been doing since version 6. >>cftransaction locks that DB actually follows may lock the whole table and you should *never* place any user code or some prolonged operation inside transaction block. cftransaction is not a panacea either: it only locks for the time of a transaction, not for the time the user will edit a record. -- _______________________________________ REUSE CODE! Use custom tags; See http://www.contentbox.com/claude/customtags/tagstore.cfm (Please send any spam to this address: [EMAIL PROTECTED]) Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:252363 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
