From: "Lee Harrington" <[EMAIL PROTECTED]> > What's the best strategy for avoiding "last save wins" concurrency > issues? If two people open a web maintenance page, change data, and > save, the "last saved" wins, meaning the person who saved first loses > their changes.
I don't claim that it's best, but here's what I do. When I read a record, one of the fields in the DTO is a checksum. When I go to update the record, if the checksum doesn't match what's currently in the database, the update fails and the user gets, "Sorry, this record has been modified since you started editing it." It works for me because the records in question are usually added as new records, and only rarely modified. -- Wendy Smoak --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
