That's what I am trying to find out. What is the norm these days? Trust the user not to change data by accident? Assume the worst? The replacement app in development by others at this point will allow the user to change nothing without first asking permission (via the edit button). Consequently productivity will be slowed (although this not a heads down data entry situation, more of a custom service env.) And the screen is full of edit, save, cancel buttons for various areas, and the popups have edit, save, cancel buttons. The entire screen is readonly until the user chooses edit. So I ask, Is this how it's done these days in the enterprise? I know as a software consumer I don't face these hurdles working with software. Sorry this has wandered off-topic. I guess this is more interface design and standards related.

>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.
>>>
>>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