For all kind of syncing there will and will always be problem with connections since you can not guarantee that is will always be there. For that to be handled as good as possible I recommend you to have a look at 360Works MirrorSync that will handle the lost of connection and continue where the connection where lost in your Sync to make sure you are up to date with data on your FM Go solution
Thank you, Johan
I appreciate your answer, and normally would look into it.
However, I want to try to avoid third party software.
Also, theoretically, the file should never be "offline".
You can always try to handle connection lost in your scripts and with triggers, but that will not make your users happy because then you have to handle connection check every where all the time. MirrorSync have been around for many years. Is very stable, fast and best of it all continue where it lost connection. That is almost undoable in a FM script
How often do you restart the server that is hosting the FileMaker Server. Whenever I see disconnect issues a restart of the server solves a majority of the problems. At a minimum a restart should happen every month and weekly is probably better. Is the iPad stationary or can if moved around? The biggest problem I see with connection issues is closing the cover on an iPad while connected to the server and then moving to a new location and opening up the iPad.
When I had the file from the server instead of the local one, the disconnect is because we had set up a server to close a file after 4 hours if it hasn't been used (which is useful for the other files on the same server). The local doesn't disconnect, as it more just doesn't connect to the server in the first place. (If I try to open the server file directly it opens.)
The iPad would be stationery and would never turn off (and never sleep), and never have a cover put on it as it will be in a case that won't allow any of that.