For some reason, I'm no longer able to run my own compiled EXE's from my OWN development machine. VFP6 Sp3. I get the "Cannot locate the Microsoft Visual Support Library" when I try. This started a month ago and as a temporary work-around, I placed a copy of VFP6r.dll and VFP5enu.dll at the same directory level as the EXE. It worked beautifully only, I still think something's wrong.

Mind you, both files (VFP6r.dll and VFP5enu.dll) are in my C:\WINNT\SYSTEM32 folder. When the problem started, I even tried running REGSVR to manually register these components to make sure they were properly registerd in the Windows registry for insurance. That didn't change a thing.

Some UT folks here suggested building a dummy project with just the bare minimum to get the run-time components in the distribution wizard to get the engine into where it needed to be. I did that. No diff.

So as a last resort -- and hear me out, as a LAST RESORT -- I uninstalled Visual Studio completely, SCANDISK'ed, DEGFRAG'ed, and reinstalled Visual Studio 6, applied SP2 and SP3 in its entirety. When it was done, guess what?

Same problem.

       "Cannot locate the Microsoft Visual Support Library"

Someone suggested a "pathing problem" and now I'm suspicious. Is there something in the Project Manager or elsewhere in my project that tells a compiled EXE where to look for the run-time DLL's?

I didn't used to have this problem and this software is not new -- we've got hundreds of users successfully installing and running the darn thing but what could possibly be wrong with my development machine?

I'm not proud so I don't mind asking: Did I do something wrong somewhere? Why is this suddenly happening? This sort of phantom stuff doesn't build any confidence in the product which I know is otherwise great.

Anyone out there have an idea or similar experience and how did you "fix" it? If it's the registry, then I'm hosed. But if it's something "logical" then what could that be?