>What Thomas said was that when the EXE holds dbf's, it shouldn't be loaded over the network for performance reasons. He then went on to add that the way to handle this was to have a small loader program that brought the new exe to the desktop when the user logged on. Just practical advice to make that particular choice runs smoothly. These are things known by those who do these kinds of things (we hit SQL Server but certain DBF's that are readonly are in the EXE, and we've used a small loader to handle updating of the EXE and other related files for at least 15 years).

Ditto, except it's 12 years in my case... but the loader was written before I got there. I only added more checks and more files to copy locally (bunch of dlls/flls and then a textfile containing the list of other files, so the vcxes and prgs with custom add-ons were also copied to local drive).