Maybe I should explain little more clear on how I did it (and would apply it towards VFP 6.0 likewise). What I do is DISABLE all the fields on the form, and have a "Edit" button. In "Edit" (ClickEvent), it would have RLOCK() somewhere (I use R to make it easier to read). If successful, then the record is allowed for editing, if not, then a Messagebox() would display (or WAIT WINDOW as I did in FPW 2.6) that it "can not edit at this moment". So, that way, the others can look at the same record.

There is only one problem (or at least I forgot how I did it in FPW 2.6) on how to REFRESH() the data on the other forms (if opened) that the record was just edited and the other user(s) that are looking at it while it was being edited. At this point (little Off Topic), what or how do you (anyone) do this, via refreshing the forms that others are looking at it? Maybe a Messagebox telling them it was "just updated, please refresh this form"? Anyone aware of Novell's "whohas.exe", could that be done with it????

I am not aware if most VFP or any app developer do not have "Edit" feature? I think it is safe way that there can be no mistake if bump a key, overwriting something. I have a buttonbar that I use on almost all the forms (Save and Revert only ENABLE upon clicking the Add or Edit):

Add    Edit   Save   Revert  Delete  Locate  Exit

Chuck

>The main problems with RLOCK() (equivalent to LOCK()) seem to be 1) the unnecessary network trafic (records are locked even if the user later decides to discard them), and 2) another user might be locked out of a record, even if the first user is only looking at a record. Or else, you provide a button to "enter edit mode" - an additional inconvenience for the user.

>>As I thought about this one... even though it's old fashion, it seems to be an ideal settings for me. I mean it would only allow ONE USER to edit it, regardless how powerful our development tools are today. When a second user trys to edit an open record, PING "Sorry, another time." Like I said, I haven't used OLDVAL(), CURVAL(), etc, so I don't know what those really does.