>I agree with Nadya: Optimistic table buffering is the way to go. You can simulate row buffering by not allowing the user to move the record pointer and using the tableupdate >command with a 0 or .f. value for the first parameter to update just the current record.

>You can also check for conflicts between two users who are editing the same record by calling the
>checkconflicts method in the _datachecker object in _datanav class (the message it provides is crude but users will probably never see it anyway).

Gerry Thanks So MUCH!!!!
I found that Class and copied it into my project manager
then in the init of my form I did this

SET CLASSLIB TO _DATANAV ADDITIVE
PUBLIC oChecker
oChecker = CREATEOBJECT('_datachecker')  

Then in the click event of my commandgroup I put

lnItReturned = oChecker.Conflictchecker()
IF lnItReturned = 2
    MESSAGEBOX('SOME MESSAGE')
    *** REVERT DATA
    RETURN
ENDIF