A person looks at a layout of a solution I built. He/she mistakenly edits a field (w/o knowing they'd done it) and then move on to another record or layout. That change is permanent. Has anyone worked up a solution to make changes to any field require user approval?

Such as a pop-up box "You've made changes to this record, click yes to save, no to revert". It feels like there's a way to do it, but I'm not sure of the logic that would go into it.

Thanks in advance for any help!

- Michael

In Layout Setup there is a check box for "Save record changes automatically" by default that turned on. Uncheck it and that should be what you need.

There are several approaches to preventing unwanted data entry changes. FM's default behavior is to let the user edit data freely.

Here are some options:

1. Lock the record once the initial data entry is done. How?

a) have a "Finalize" script that runs that sets a field to 1, ie, flag_locked. Use access privs to not allow editing if flag_locked=1.

a duplicate layout that has the field behaviors set to NOT allow entry in Browse Mode. Your navigation scripts take the user here if the record's flag_locked = 1.

a + b are often both used together.

2. Perhaps only some of the fields are so sensitive that they should be locked? If so, use a button next to the fields (or group of fields) that calls up a new window with just those fields on it (a popup layout). This button may have a trap to only allow "admin" access. If all fields need protection from editing, then you need two layouts and a button that switches btw them when Edit is clicked. However, this will not allow a user to Cancel edits...

3. Have an Edit button on the layout. This takes the user to a duplicate layout, but all the fields are actually global field twins set to the current record's values. (Lots of work). On this "Edit" layout, a user can click Cancel, which just switches them back to the browsing layout and discards any edits they made in the Edit layout. Or, they click Save, and your script sets all the fields to the global twin.

I often use 2.

Another topic to research are Audit Trails (storing previous values and dates of edit).