I have a client who is reporting an issue with FileMaker Go 12 closing unexpectedly.
The database app I have created for them records the issue of outdoor, ski equipment, etc to students at a camp that has new groups of students each week.
The clients reports the following:
1) Open Filemaker Go app
2) Select the file to open
3) Once the opening screen is displayed they update data on the iPad from central database via a script attached to a button
(The script tests for a connection to the central database, opens the central database as hidden, imports the data and closes the central database file. Subsequent screens show only fields from TOCs that are local to the database on the iPad)
4) Move down to the student issue room that is out of WiFi range with the file open
6) Start entering the students data
7) The 3G is also marginal at this location, and when the signal drops from 1 bar to 0 bars FileMaker Go can close unexpectedly - data is lost.
I'm wondering if I have missed something or is that FileMaker Go is closing unexpectedly because it hasn't properly closed all references to the central database file.