>>Hi,
>>
>>In my deployment of the VFP 9 application all necessary DLLs are placed/copied to the application folder. I am talking about these DLLs:
>>msvcp71.dll
>>msvcr71.dll
>>vfp9r.dll
>>vfp9renu.dll
>>vfp9t.dll
>>
>>So the above files are in the folder
>>\\servername\appl_name\
>>
>>So far so good.
>>
>>But I need to run a small .exe in another folder (e.g. \\servername\appl_name\error_log). And, unless I copy the above DLLs to this folder, the EXE won't run.
>>
>>I would prefer not to have to copy the same DLLs in various folders. So, my questions. Can I set the Path to the required DLLs into the config.fpw file? Or some other way to make the .EXE "look" in another folder for the DLLs?
>>
>>TIA
>>
>>UPDATE. I think I don't have to use config.fpw. I can use another text file where the Path will be stored. And in the small EXE app open and use this Path. I will try this.
>>
>>UPDATE 2. Using my own configuration file where the Path is stored didn't work. The problem is that VFP 9 app does not even run to begin with. So, it cannot open and read configuration file. It has to be done differently. This is why I thought that config.fpw should provide the answer. But I don't know how to set Path in this file. Or if it is possible.
>
>Another good reason the register DLLs so all your applications do not need to look for them.

This approach has advantages.