>>>> I had to do this too, install the DLLs (run a dummy setup) to run EXEs
>>>> outside of vfp on my own PC. Someone on the UT suggested it at the time I
>>>
>>>> got vfp5, so I just assumed it was a normal process. I guess not?
>>>
>>>it works here - I don't remember doing anything special ..
>>>
>>It certainly seemed strange to have to run a setup on my own PC. (s) But the advice worked, whatever was wrong...I'm quite sure I tried re-installing vfp at the time, but that didn't help things. Incidentally, I didn't have the problem on my home PC, so I guess it was an unusual problem, in retrospect.
>
>Bruce, I had the problem on one computer only, also. I tracked it down to a Win95 problem, finally, not VFP. Win95 wasn't checking its own system directory for DLLs, so it couldn't find the VFP files there unless VFP was loaded. I finally ended up adding the system directory to my PATH command, and this problem AND my problems with the CONFIG.FPW files went away. Very strange!!
>
Glad you solved it...perhaps my problem was something similar...I've noticed I have duplicates of some DLLs in my C:\WINDOWS\SYSTEM and my C:\SYSTEM directories on my work PC, but can't clean it up without causing trouble in one app or another...oh well, as long as everything works... :~)