WINDOWS kbinterop kbenv kbusage kbsetup kbprb The information in this article applies to:
SYMPTOMSIf ODBC 2.x drivers pass function calls to the ODBC 1.x Driver Manager, you may receive the following errors from any 16-bit application that uses ODBC on a Windows 16-bit environment (such as Windows for Workgroups 3.11 or Windows 3.1).
-or-
CAUSEEarly versions of the ODBC Driver Manager (1.x) were placed in the Windows directory on 16-bit Windows platforms, while subsequent versions of the ODBC Driver Manager (2.x and above) were placed in the Windows\System directory. The best way to determine if you are encountering the problem is to search the computer for the Odbc.dll file, and verify the version in File Manager. You can do this by clicking on the file and then clicking Properties on the File menu. If the first possible Odbc.dll file in the path is the ODBC 1.x Driver Manager, you are most likely encountering the problem. WORKAROUNDTo work around this problem, remove the ODBC 1.x Driver Manager (Odbc.dll) from the path and/or place the ODBC 2.x Driver Manager (Odbc.dll) in the path first. MORE INFORMATIONThe following portion of an ODBC Spy trace was obtained from an instance in which the error reported was "ODBC Call Failed" from Access (the SQLSetParam was replaced in ODBC 2.0 with SQLBindParameter):
Additional query words: 1.xx 2.50
Keywords : ODBC SSrvGen |
Last Reviewed: August 24, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |