What you are describing would need additional functionality since the updlock with SQL server doesn't prevent data reads occurring when lock is in place. There are about a dozen ways to implement what you suggest and definitely something like that had to be done. I would even add messaging to that solution.
TK ----- Original Message ----- From: "Claude Schneegans" <[EMAIL PROTECTED]> To: "CF-Talk" <cf-talk@houseoffusion.com> Sent: Friday, September 08, 2006 11:34 AM Subject: Re: Locking Theory > >>So what happens when a user has made all his or her updates just to > be told > "We are sorry but the record you are trying to edit is locked" > > Actually, this is not the way it works. > When a user reads a record for editing, the record is locked until he > updates. > During that time, when another user wants to open and lock the same > record, > for the same purpose, THEN he will get the message "sorry, this record > is locked", > BEFORE he edits the record, not after. > So for him, there is no time waisted, it's just the time for a coffee > break ;-) > > -- > _______________________________________ > 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:252565 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
