True, it's pretty much the VPM approach, maybe I'm just afraid of careless users that just assume "Yes" is always the way to go without actually reading a message.

While testing the forms I found myself overwritng part numbers and stuff, kind of used to having the focus on a search button to go straight to a given item, of course there's always revert. I guess it all depends on the type of users, access control, and sensitivity of the data. Or perhaps I'd have to take the place of a data entry guy for a day or two and see if it's a PITA having to hit that edit button all the time.

>I don't use edit buttons in my forms since TableRevert() came along. Since it's easy to revert a change, I won't force user to do an extra step to change a field.

---

>I recently started using VPM, and was surprised that they don't implement an edit mode by default, they recently added some functionality to do so, but it's not fully supported, in their documentation they say that having forms always in edit mode was a more common practice since VFP came along.
>>
>>I've always used an edit mode, and prefered it, because it's harder to mess things up this way, so I was surprised to hear that this was an "uncommon" practice ... what do you all think?, do you use an edit mode?