>What about treating like optimistic buffering. Multipl users could get the same for editing and when save attempted you might compare the values you posted with the ones in current record and decide what to do.
>Cetin

That certainly is an option. It actually is my top option at the moment. I thought I would always keep the original value of the record as I received it and then each field that was changed by the user gets checked against the original value and if that field was changed by some other user make some sort of decision of what to do. May have to let the user know about it and let the user make the decision. It certainly sounds fine but, of course, the implementation of that idea is the hard part. It takes much machinery to make that happen in a manner that is not cumbersome to the users or time-consuming.

So anyhow, still interested in hearing from someone that has done this.
Anyone out there ?