<snip>
>>Wait a minute, Pascal. You're using pessimistic buffering but you're not >having a problem with determining changes made by another user? What are you >doing that I'm not? My problem arises when User1 is viewing a record, User2 >then makes and saves a change to the same record, User1 then decides to edit >the record, but his form is still showing the record as it was before User2 >saved his change. How can you trap for this?
>
>Bonnie,
>you're pointing out a problem here that I wasn't aware of ; I think that as in my programs the user explicitally has to indicate he wants to start modifying I didn't have to handle this problem (I thought the screen did some kind of autorefresh as exist with browses in FP DOS).
>I'll check it out and keep you informed ...

Pascal,
Yes, the problem exists only when there is not Edit button and the user implicitly starts an edit just by typing in a field. Funny you should mention the autorefresh for browses, cuz I was chatting with a friend last night who mentioned the same thing and that got me thinking of a way to solve this dilemma ... using a timer on the form class, I auto-refresh the form if they are not in an EditMode. Voila! Works great (not perfect, but good enough!)

Bonnie