The information in this article applies to:
on the following platforms: NT, Win95
SYMPTOMSIssuing the SET LIBRARY TO HOME()+"FPSQL.FLL" command in FoxPro for Windows and then checking to see what library is loaded shows that Fpsql.fxp is the library that is loaded. In other words, the FLL compiles into an FXP file.
CAUSEThis is caused by a missing DLL file. Usually the missing DLL file is Odbc.dll but sometimes the FLL could compile if another required DLL is missing from the Windows\System folder.
RESOLUTIONMake sure the Odbc.dll file is located in the Windows\System folder if using Windows 95 or Windows 3.x. If using Windows NT, the Odbc.dll file should be in the WinNT\System folder rather than the WinNT\System32 folder.
STATUSThis behavior is by design. An FLL cannot be loaded if all of the DLLs that it depends on do not exist.
MORE INFORMATIONThe Fpsql.fll and Odbc.dll files are provided with the FoxPro Connectivity Kit. The Fpsql.fll is on Disk 1 along with the CKSample.app and some other files. It is not a compressed file so it can be copied directly from the disk. The Odbc.dll is on the ODBC Setup disk. It is a compressed file so setup for ODBC should be run to install it. Steps to Reproduce Behavior
REFERENCESFor additional information on other files installed with the FoxPro Connectivity Kit, please see the following article in the Microsoft Knowledge Base:
For a utility program that can be used to test if a FLL file will load, see the following article in the Microsoft Knowledge Base:
Additional query words: Keywords : kbtool FoxWin FxenvOs FxtoolCk Version : 2.5 2.5a 2.5b 2.6 2.6a Platform : WINDOWS Issue type : kbprb |
Last Reviewed: August 20, 1999 |