Auto committing - can I prevent it

[christw]

There was a similar post with this title but I didn't get what I wanted from it. I am setting up a layout for data entry. I have placed three buttons which when clicked will either save the current record and start a new one, save the current record and exit to the previous menu (layout) or cancel data entry and go back to the previous menu.

 

The save buttons will perform a script which will include all the validation of the entered data in a particular order and will send the user to the first wrongly entered field until all the data is entered correctly. The problem is that if you click anywhere on the layout outside a field, filemaker asks you whether you want to save the data or not. If you choose yes, the data won't be filtered.

 

I found a workaround by placing a background box which I turned into a button but without the hand cursor. I put a script which goes to the next field and then back so the net effect should be no apparent effect to the user. The problem is that the background, being a large button, flashes a different colour (like any button) when clicked and it's not very aesthetically pleasing to see the whole screen flash when you click outside a field.

 

Is there some other way to work around the auto commit feature in a cleaner way?

 

Chris

[Ender]

Hey Chris,

 

The problem is that if you click anywhere on the layout outside a field, filemaker asks you whether you want to save the data or not. If you choose yes, the data won't be filtered.

I'm not clear what "won't be filtered" means. But if you want to work around the way records are committed, you might try a technique like using global fields for data entry and editing, and have a script set the results. A similar idea is available for download here:

 

http://www.foundationdbs.com/downloads.html

(look for the ViewerTable Demo)

 

where the edits are done in a Preference table, and moved back and forth via lookups.

 

Personally, I just turn off the Commit notifications by setting the layouts to "Save record changes automatically", and then use passive validations and scripts to update the status of things.