Have you tried using the "Open File" script step to specifically open the remote file at the start of your script?
You could also try the "Refresh Window" script step with the "Flush external cached data" option checked.
You may in fact need to use both commands, open the file, go to the layout based on the hosted file and then refresh the window.
Tks for the update.
I was thinking about the 'open file' for a while but never tried it because I am not actually opening a remote file, only using a layout with a table using related files. The iOS app only has one file, the remote file is not present on the iOS. However your suggestion makes sense, I did not tried but I will. The other suggestion makes sense as well and I did not use that either, but familiar in my local desktop app and widely use for various reason.
I will try this and let you know,
Regarfds, Martin B
Looks like this will work, still difficult because the variance with iPhone models and performance, as well as wifi and wireless reliability. However the reconnectivity is working and this will help a lot.
Look into the fmreauthenticate extended privilege. You can set it so a user can be out of a database for up to a week before having to log back in. It may help.
I shut off this feature because 'all' users re-login everyday, and I have the server disconnecting users after 7 hours of inactivity. I keep this option un-checked so user are not forced to reconnect when moving to other apps, which is often the case.
The main issue that I did not consider at start is the variance in iPhone model/performance, and the variance in connectivity from 3G to strong WiFI network. User with iPhone 4 and located in rural area with weaker WIFI and Wireless network are more subject to 'disconnetion', yet it is not rare either in major center with newer iPhone 5 to experience the same issue.
The file is local on the iPhone and can work without hosted files, but new 'jobs' requires the connection to be pulled on the IOS. It still works because I added a backup process that sends a SMS and/or Email so the job can be done, but it is not perfect.
What causes the biggest frustration, when the connection is lost a IOS generated message is asking the user to 're-connect' and if no connection is available the user most say 'no' to re-connect. If this error control could be avoided and let the user carry on without having to reconnect and let the script do the reconnection, while displaying the 'connection status' it would work better. The users are not always carefull and don't manage IOS prompt properly sometime which is more challenging for them.