On Oct 4, 2019, at 5:24 PM, Chuck Miller wrote: > Good thought but when you have a but client a new 4dlink file gets created on > connection and that is the one that is used
If you are using a “built” 4D Client, then the 4Dlink file is not an option because the build client uses it’s own internal .4Dlink file. But if you are using standard 4D Server and 4D, then you can do what I specified. Since you are deploying in a very controlled hospital environment, I would suggest you put this back on the IT department. They make all the rules and make it difficult. So make it their problem to solve. If they want to make it easy, they can do the DNS change work. If they want to make it hard, they can deal with how to make it work. You know what needs to be done to get 4D Client to connect to 4D Server. Tell them how it works and then ask them “how do you propose we solve this problem”. You would be surprised how quickly they decide what is “completely impossible” become easily done when they have to make it work. Remember that it is their sandbox that you are playing in. You are just a third party vendor. If they want to make it difficult, that’s not your problem, that’s their problem. And the users need to know that. Tim ***************************************** Tim Nevels Innovative Solutions 785-749-3444 [email protected] ***************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
