Hi.

Here's something to consider! Does the user have to click edit first? I'd agree with clicking add. As long as there are save/cancel button(s) does clicking an edit button really matter?

>>>Newbie question for VFP6:
>>>
>>>After devouring several books, scouring the Codebook6.1 framework, and looking over the FPD2.6 and FPW2.6 code (probably what is confusing me) that makes up the apps we are currently running, I still don't quiet understand how to set a form so users can browse existing records and then unlock the records for editing. New, Save, Cancel I've got a handle on OK, but can someone point the way to edit nirvana, I don't mind the rigors of the journey, I'm just not seeing the path.
>>>
>>>With humble thanks to all you knowledgeable ones.
>>
>>The usual way to do this is NOT to use explicit locking and unlocking.
>>
>>Use buffering (usually optimistic - may be table buffering, or record buffering). See cursorsetprop("Buffering")
>>
>>Save changes with TableUpdate().
>>
>>Undo changes with TableRevert().
>>
>>HTH, Hilmar.
>
>User opens a form, pulls up the client or order they would like to make changes to, clicks on the edit button on the form, enables making the changes to various fields, and then click to save or cancel the edits. Is this not the way things are done now? All I have for a working reference is FP2.6 apps. I understand that scatter memvar memo...gather is not the the preferred method for working in VFP, so I am trying to grasp the visual and OOP methods of protecting data from accidental changes other than a message box to "save changes or cancel"
>
>Thanks