You state the files were copied to the "c:\windows\system" directory. It should be the "c:\windows\system32" directory. Better yet, to avoid having it in the system32 directory, put it right in the application directory.

I don't know if that will help, but its worth a shot. Is it possible you (or they (rolling eyes)) compiled the program with version of VFP ? Cause I don't know why a FPD/FPW 2.6 app would be looking for a VFP support library. My suspicion is someone there is busy trying to 'update' it and has just enough knowledge to be dangerous.

John G.

-------------- Original message ----------------------

From: "Hines, Catherine" <catherine.hines@lmco.com>

>

> We (in this department) have a small FoxPro executable written in FoxPro

> 2.6. It's been running fine on a dedicated machine in the customer area

> until about six months ago, when the users determined that they needed

> to both move it to other desktops and to modify it. We haven't yet

> tried to modify it because we can't get it to run on my desktop but

> mine, so far. I have VFP 7.0 installed, as well as 2.6.

>

> The new users - the customers - get the error message above, which is

> pretty surprising since 2.6 is pre-VFP but I assume it is a Windows

> thing. I'm using Windows XP Pro 2002 service pack 2, as are they.

>

> I looked this message up online and found the recommendation to copy two

> files (vfp6r.dll, vfp6renu.dll) to c:\windows\system directory of the

> desktop with the problem. The tech guy has done that, but is still

> getting the error. My desktop has the vfp8 version of those files; the

> directory containing the executable that we're trying to run contains

> the vfp5 versions.

>

> Any suggestions? We added the directory containing all of the Fox DLLs

> to the PATH statement on the desktop, but that did not solve the

> problem, either.

>

> Catherine Hines

>

>

>

>

[excessive quoting removed by server]