>Whoops, sorry guys about that emtpy post.
>
>OK, here's the real scoop on MSVCRT.DLL.
>
>First, I seriously doubt if it's related to the problem. The following is from MS Knowledge Base article Q156976.
>
>"The version of files MSVCRT40.DLL and OLEPRO32.DLL in Windows NT 4.0 and Visual C++ 4.2 are wrapper DLLs that call functions in a new file, MSVCRT.DLL. The file MSVCRT.DLL is included in Windows 98, but not in Windows 95 or Visual Basic 4.0."
>
>Since I ran foxtools in both VFP 5.0 and 6.0 on an early version of Windows 95 without problems, it may not be the problem unless the DLL shipped with VFP.

Hi George,

If you look at FOXTOOLS.FLL (VFP6) with DEPENDS.EXE, you'll see it uses MSVCRT.DLL. And I think I remember seeing it in a build using the Setup Wizard. I used the Setup Wizard only once, though. Always found it lacking, to put it kindly, even in the old FPW version. Used to use INSTALIT for FPD/FPW apps, and now we use PCINSTALL. I don't handle the installation stuff anymore, so I really don't know. I just looked at one of our CD's for a VFP5 app, and it has MSVCRT40.DLL on it, but not the other one. I don't have a VFP6 app CD I can look at to see what's on that available right now.

I just looked at the FOXTOOLS.FLL from VFP5 and it specifies MSVCRT40.DLL and the FOXTOOLS.FLL for VFP6 says MSVCRT.DLL. I wonder why the difference?