Actually, the LAN is Novell 3.21 and it doesn't support long file names.

Now there is another issue. At least part of the reason VFP can't instantiate my DLL is because the MSVCR70.dll didn't get copied or installed, in spite of the fact that the VC++ runtime was checked to be added as a merge module. Does it make any difference which instance of the VC++ library I check? It's in the merge module list multiple times (at least 6) but I checked the one near the VFP runtime libraries entry. When I try to register this file using Regsvr32 I get a error message stating that "The file [correct path and file] was loaded but the DllRegisterServer entry point was not found... it may be a corrupt version ... use pView to remove it." I can't find any references to PView on this machine (Win2KServer.) I also don't see how it could be corrupt if it runs fine under Win98...

Also confusing is the fact that InstallShield put my DLL (the whole reason for the install in the first place!) in the "c:\program files\common files\microsoft shared\vfp" directory along with the vfp runtime libraries in addition to placing it in the [installdir]. Is it supposed to do this? The one in [installdir] is the one that is registered.