I am still struggling with this issue. I thought all the data separation developers would have some sort of input on this.
So I happened to take the time to see what I was looking at.
In the ESS setup window for the file path it is possible to enter a number of locations for the same file in an order of priority. First issue solved! Not sure why I did not notice this earlier or why no one bothered to mention it.
Second issue is still a pain and is a FM issue. I will work around it with different layouts for now.
Just out of curiosity, why don't you host the UI file on the server? I did some tests and did not find much speed diferences between a UI file on Go and hosted on the server, that would solve the issues with the connections to the data.
If your first file determines if the user is in the office or outside and uses an Open Url to open de UI file with the correct address, now can you make the first file so clever that you can store offline info in here? than you would only need 1 file on Go.
it may depend on the UI file! I have a client with a very complex UI. It can be hosted 'in office' (FMS) for office users, but also can be placed directly on the laptop (or iPad). I can attest that it is MUCH faster this way when accessing the 'data' files remotely (out-of-office).
Interesting. I did some testing when I was building a system hosted with an external hosting party and found no big differences then.
Since then the system has evolved, so I can do some more testing to see if things are changed.