The no edit button approach is definately best from a Windows UI guidelines approach.

>I have been trying to design a base class windows data entry form and now find myself at a crossroad as to weather I should use an EDIT button on my form. Most of the sample apps I have seen use the EDIT button to toggle the Read Only property of the various data bound controls. However I like the technique I have used in VFP where instead of an EDIT button, when the user makes any change in the control, code added in the base class event handler will automatically send the form into edit mode. VFP has events in all controls that make this very straight forward but I’m having some trouble implementing it in .NET. Seems there is no common event in the controls to trap interactive data changes made by the user.
>
>What do you think is the best approach?
>
>I don’t want to swim upstream on this issue, if the EDIT button is the way to go then I will just go with the flow.
>
>Thank you for your freedback,
>
>Terry Carroll