Not that votes mean anything, I think that Ed is right about this one. If the whole EXE was loaded, why would the EXE file be "used by another process" if you try to make changes to it?

Also, I think it is generally a better idea to run EXEs off a local drive if possible (eg. there is room, etc.). The only problem is version maintenance, which a loader program will fix.

As far as where to get the data from, I prefer to use a local configuration DBF which contains pointers to file locations. This allows future flexibility. One example would be a new database is being used by the company. It is located in a different directory. A field can be added to the configuration file that holds pointer information for that directory and anywhere in the code that you want to access that database, you would use the configuration file's information. No hard-coding of data locations. Also, for example, \\JOHN\C-DRIVE crashes and it contain some data. Fine. Restore the backed-up data to \\PAUL\D-DRIVE, instruct the users to change their configuration file pointer information, and you are up and running.

Just my thoughts.

Take care.