Optimistic Concurrency Question:

How do you guys manage conflict resolution w/ optimistic concurrency?

I've never bothered with this before (shame on me yes). I have a little project coming up that I am going to try using OC with conflict resolution. I have to say, standing outside the gate it sure looks like more trouble than it is worth.

What is best practice for resolving update conflicts? I am thinking of a Conflict Detected form containing conflicting data the user can save or write down, followed by an automatic reset of the data to the state of the most-recently-saved record. Kind of ugly, but best I can think of offhand. Is there a smarter way?

Matt Received on Fri Oct 18 2002 - 11:58:48 CDT