Having seen the same thing (described below) in several apps installed in several user locations, we are using an Edit button for just about all our applications now.

Example: a Product form with a Product Type lookup is brought up by the user. The user wants to find all Products with a given Product Type. The user changes the value of the Product Type on the Product form and pushes Save. Ouch! Having the Edit button educates them as to what they are doing. Once in Edit Mode we let them stay in edit mode so long as the PK of the parent entity on the form remains the same, so they can do whatever they want without having to click it for related entities that may be on other pages of a pageframe, etc.

Just an observation from the field, as it were.

Hank

>Adding an edit button is not needed and takes away from the interface. When a value is modified that should trigger a change in the forms "Mode" requiring the user to click a button to perform the edits is an unnecessary step.