Al,

I had already tried this in my experimenting but it didn't help. Sergy sent me to a web site that had the answers that I needed.

Thanks,

Robert



>Not tested, but have you experimented with including the path to the SystemFiles folder (e.g. C:\VfpApps\SystemFiles) in the PATH >environment variable? A VFP .EXE *might* be smart enough to check that PATH for the runtime (that's what I haven't tested).
>Regards. Al

>"Violence is the last refuge of the incompetent." -- Isaac Asimov

>Al

>>I have a client that does not want me to put any of the VFP runtime file in the \WINDOWS\SYTEM32 folder. This no problem because I can obviously just drop them into the root directory of the app but I was wondering; can you use one set of DLL's with muliple apps in differnt subfolders? For instance, with a directory structure like the following:
>>
>>\VfpApps
>>\VfpApps\App1
>>\VfpApps\App2
>>\VfpApps\App3
>>\VfpApps\App4
>>\VfpApps\SystemFiles
>>
>>Is there anyway to place one set of runtime DLL's in the "\VfpApps\SystemFiles" folder and have the EXE's in the App1, App2, etc. folders reference that location. I've tried numerous things but I can't seem to get this to work. It, of course, works if I put a separate set of DLL's in each of the "app" folders.

>Robert