1 of 1 people found this helpful
In FM15 reconnecting work much better. I also check to make sure I always have connection to FMS
As Johan correct write, it is much better in FileMaker 15, if the connection is lost.
But the main problem is that to give your users a good work experience you will need one of two (or both):
- A stable internet connection. And you may have to accept reconnecting when changing network (loosing network connection and connecting to another network).
- An offline sync based solution that will make sure that the user can work while data is kept updated when the connection is working.
May I ask you a question: Why do you not consider a sync/offline model?
With FM 13 and it's respective go version, I used an on timer script step trigger that would be timed to before the sleep timing on the iPad. It would remember the field that the user was in, commit the record and go back the that field.
I suppose if I wanted to, I could have remembered the cursor positioning as well, but it was never really an issue, as the event would only trigger when it was idle. Forcing a commit is not ideal, but it gave me some sense of certainty and never seemed to annoy users.
The main issue is with changing networks. I do not see why an offline/update model needs to be used when a connection is always available, but changing.
Reconnecting in 15 looks like it might be better but when presented with the reconnect dialog and entering credentials FMGo always locks up and needs to be restarted just to login again. This happens even when the network doesn't change and with Pro as well if the computer sleeps even for a few seconds.
This is the #1 usability issue I have with FM right now. Should the LAN connected Pro clients run an offline/update model as well? I think not. Current fix is that all LAN connected Pro clients never let the disk sleep.
Maybe there is just no way around this issue in FMGo right now besides offline model.