HOWTO: Ensure ODBC.DLL and ODBCCURS.DLL Cursor Levels MatchLast reviewed: June 26, 1997Article ID: Q127734 |
The information in this article applies to:
SUMMARYThe ODBC Driver Manager and the Cursor Library must have the same cursor level. ODBC.DLL and ODBCCURS.DLL are the corresponding files in 16-bit Windows. ODBC32.DLL and ODBCCR32.DLL are the corresponding files in 32-bit Windows. Attempting to use these dynamic link libraries with mismatched cursor levels will cause the cursor library to fail to load. If the cursor library fails to load, the recordset will be a forward-only, read-only recordset. The following message may appear in the trace output when this condition exists:
Cursor library not used. Version mismatch with driver manager State:01000[Microsoft][ODBC DLL]In some older versions of ODBC.DLL, this message may not appear even if the Driver Manager and Cursor Library do not match.
MORE INFORMATIONTo ensure that the Driver Manager and Cursor Library have the same cursor level:
What to Do If the Driver Manager and Cursor Library Do Not MatchIf the Driver Manager and the Cursor Library do not match, reinstall the latest ODBC Manager by running the ODBC setup from either the Visual C++ CD, the latest ODBC driver pack, or the ODBC section of the Level II MSDN CD. If the cursor level for the Driver Manager and Cursor Library do match, but the trace message listed above still appears in the output, check to ensure that an older version of the DLL's are not anywhere in the path of the program.
|
Additional query words: 2.50 2.51 2.52 3.00 3.10
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |