>>Your .FLL file is trying to return some kind of error, and it can't, so FoxPro thinks it's a program and tries to compile it. More than likely, since this is only happening on one machine, that machine is missing some other .DLL file that your .FLL file is dependant on. If you have Visual Studio, there is a DEPENDS.EXE you could try running on the .FLL file and see what other .DLL's it is dependant on. It's probably MSVCRT.DLL or MSVCRT2.DLL that's missing on the one machine, but that's just a SWAG.
>
>Thanks for the depends.exe! I could not find out why mscomm32 was not working on 1 machine and that exe allowed me to find the missing dll.
>
>Thanks a bunch.
>
>__Stephen

Another useful tool is the VFP Class Browser to look at .OCX files, etc.
Doesn't help with the dependencies, but now you've got the tool for that, too.