Error capture on and run a dummy script from the hosted file
I think the issue is that when the ipad file gains connection (after previously not having it) it keeps in memory that the "server hosted" file is not available, the only way to force it to search for it again seems to be to close it and reopen it.
Is there a way to do that on the ipad so I could do this in advance of any testing (ie close and open)
Is this remote file on the Relationships Graph of the local file?
it is and I think that's the issue?
This file is to create the relationship to push up a record change to the server.
Importing downwards if fine..
You can't use anything else apart from build in functionality. I would try another local file with a script which will close the source file and open it again. You would have to split you script to before and after close.
Did you try using fmp protocol to reopen the file from the server and see if you can error capture that?
looks like im gonna have to code a 2nd file to handle all this.
I cant have and external data sources in this file (that is mostly offline) as it will even throw up a FMGO error about losing connectivity.
a bit more work but cleaner..
I do it in multiple stages:
1. First check if you are online at all... (Get an url from somewhere without an error ) on error WiFi is probaby cause or location is offline.
2. Second do an insert from url with a test file from FileMaker Server Web Server, on error VPN is probably down or server has a problem
3. Last open the sync file, that file tries to open a FM file on the server. (The time out is pretty long on this, that's why I use the other steps first and you can tell the user what's the problem. Otherwise they blame the solution... when it might just be the local WiFi or internet access.
well thanks to you all, I did have to do a separate sync file and it was a fair bit of work with lots of curve balls.
i send the files via email to the iPad users and that works ok for now however I have to ask them to manually remove the existing files first as they don't get overwritten by default.
i assume there is no workaround to this one?
anyway thanks again..
The method I use involves storing the sync file in a container field in the local database, exporting it locally, and then exporting an empty file over the top of it (using the same file name). This causes FileMaker to erase the sync file. The original is still in the container field, so no harm, no foul.
interesting Mike, I will give that a whirl on Monday and see if it solves the issue, it sounds like it will work well.