Thank you for your post.
Of the two individuals that are encountering this issue, find out how often they are rebooting FileMaker Go. How often are they rebooting the iPad to clear out any possible memory conflicts? What other applications do they also have running? Also, find out what actions they are performing with FileMaker Go. Any one of these could be a contributing factor to the corruption.
Here is the response to your questions from the sales rep that has been having the most problems.
- I never fully close out filemaker go, nor do I close the file. Will typically just pivot to another app.
- Rarely restart the iPad
- Commonly used apps > Mail, safari, Dropbox, ibooks, groupme, PDF expert, photos, things, messages, 1password, notes, kindle, newstand, maps, contacts, videos, reminders
As far as what they do - it is a database for medical sales reps. So he occasionally adds a new facility or doctor. Makes notes. Reviews his sales data which is synced from the server.
Have the user exit out of all the applications and reboot the iPad. Once rebooted, download another copy of the database file to the iPad, and then launch FileMaker Go. The user should then be able to use the database file. If you are the developer, you may want to include a button on the layout at the end of the day that exits the application. Although you can't force the user to reboot the iPad, you can at least control them exiting the application.
I just asked the user to start closing the database when he is done for the day. Not something I would have thought to ask. Thanks. I will be back if the issue continues.