We used to do this (SoftLock) in the Fox 2.6 days and haven't been specific at the User-level since, but I am very interested in this thread...I would like to figure a way to do this myself in VFP.

The TableUpdate() command will return Record #s for un-updateable records as an Error array, if these could be captured beforehand somehow...

Just some thoughts.

-Irv.

>I'm curious how people normally handle soft record locks with buffering? (In case I have my terms wrong, I mean where you put who has the record locked and since when into the record rather than using RLOCK()).
>
>Since the table is buffered, no one else in the system will see the change to the lock status fields unless I do a tableupdate. So when the user wants to edit/add, I change those fields, update the table, and then let them edit. When they cancel or save, I have to change them again and update the table again.
>
>I just get the feeling I'm doing things the hard way. Is this normally done in a better way?
>
>Thanks,
>
>Michelle