>>About once every VFP version I cook up a form for my own use, using FFC, and get to hate it within a week. Why? The Edit button. The idea that whatever I'm doing, I have to tell my form first, otherwise it's readonly. Want a new record? Click new. Want to edit a record? Find it, then click edit. Want to move to another record? You get the "save?" reminder. It's somehow unwieldy.
>
>In your UI, at what point do you save? When exiting the form? If that's true, and let's say there were 15 records edited, how do you cancel changes to one of the 15 records?

There's a save button, sure. But editing is enabled by default. And depending on the type of the form, a new record or editing an old record depends on what the user enters in the first field etc. There's no Edit button, no New button. The user is always presented with a blank, editable record, and a way to get to an old record.

If a form is read-only, there's a reason for that - it may be a view form, or a lookup form or whatever. A data entry form is not read only by default.