filemaker pro 14 stops working when saving scripts

When FileMaker Go is in a “sleeping/disconnected” state, uncommitted changes don’t get explicitly committed…and other users can modify the record. The problem in this case is that the user is sleeping his device without committing changes so when another user modifies that record while FileMaker Go is “sleeping”, the iPad user’s changes are lost. The way FileMaker Go reconnects to the server (and now in version 14 FileMaker Pro works this way also) makes this work seamlessly for the user. Then he does some work (like replacing a window in a building) and then takes some more photos of the completed repair. He pulls it from his pocket, opens a work order, adds some photos and notes, and then sticks the device back in his pocket.

In this case, the user was using an iPhone or iPad Mini. This is custom software it should work the way the user works, not the other way around. Complaining about the user doesn’t really solve the problem, and we are problem solvers. The truth is it’s easy to complain that the user isn’t using the system as it was intended. I ran into a situation recently where a user would not or could not remember to commit their changes before exiting their FileMaker Go solution on their iPad.

Filemaker pro 14 stops working when saving scripts