Hi Peter,

Yes the relevant DLL's need to be loaded on each machine. What I did was create a simple setup.exe that installs only a resource file and the DLLs and ran this on every machine and it is now part of our new machine set up procedure. I don't believe there are any issues related to the default directory. With the EXE local and the data on the network you may need to set a relative path to the data files.

As for version changes, a loader idea is one I like. This can be as simple as a batch file that copies the latest EXE from the network and runs it.

>>Put the EXE on all local machines and only data on the server so the app doesn't have to come down the pipe as well.
>
>I'm about to start experimenting with this approach. Since I'm running on 100baseT ethernet I haven't bothered with it up to now.
>
>A couple of concerns:
>
>I assume all of the relevant DLL's should also be loaded to the client machines. Are there any issues relating to the default directory? With this approach the data tables and the EXE/DLL files cannot both be in the default directory.
>
>This approach pretty much requires some method of automatically copying the most current EXE or APP to the client machine every time they startup. Version changes become way to much hassle otherwise. I have an article somewhere that spells this out.
>
>Peter