That's the part that's confusing me. When User #2 moves his record pointer and comes back to the same record that User #1 is editing, it's as though User #2 unlocked User #1's record because User #2's RLOCK() condition is True (.T.) when he comes back to the User #1's record and presses the Edit button.

I don't know why or how this is happening. I would expect User #2 to get the RLOCK() condition is False (.F) as he did when he first tried to edit the record and pressed the Edit button and User #1 was already Editing the same record, before User #2 went to another record and came back.

Unless, there's something else causing the error like Ed Rauh mentioned when he stated that there are two different ways to get the message - record already in use. I don't know what the other way might be, but maybe it's FLOCK.