>>Caroline,
>>With a brute force update last saving user would be the winner and his/her record would be saved. With conflict managing you could test and prompt the user that there is a change (curval). There are ready class and code for it. I don't remember the location and names now. On MSDN help check section about views. Idea is to try an update (not forcing overwrite the changes) and if fails traverse the fields with oldval(), curval() comparison.
>>Cetin
>
>Cetin,
>
>That is what I have been trying to do however if you are using a view (buffered) then CurVal doesn't return the disk value ie value changed by another user!
>
>So a comparison is not possible!
>
>Thanks for any assistance.

Yes views are buffered but why ? curval() returns on disk value. You could test that with an SQL select which always returns on disk values.
Cetin