1 of 1 people found this helpful
One option would be to use a VPN. Then you would always use the LAN IP to access the server. This also adds a layer of security in that your server would no longer open to direct attack (assuming you also turn off port forwarding to the server). But it also adds a step for users to connect when remote.
Another option (and this is a little painful) would be to have either two UI files (one for local and one for remote) or two login buttons on the UI file and two sets of layouts, one for each data source, and just use the appropriate one for each location.
Kevin and Mike, thank you for your replies. Yes, VPN is something we had in mind as it adds an extra layer of security, but we're not sure if this extra step for users will be acceptable. Mike, having two UI files is something we would like to avoid if possible. Thanks anyway for the advice!!!
Well, there's still the option of a single UI file with separate layouts for each data source.
But it's still not a nice situation, no matter what you do.