HOWTO: Ensure ODBC.DLL and ODBCCURS.DLL Cursor Levels Match

Last reviewed: June 26, 1997
Article ID: Q127734
The information in this article applies to:
  • The Microsoft Foundation Classes (MFC) included with: - Microsoft Visual C++ for Windows, versions 1.5, 1.51, 1.52 - Microsoft Visual C++, 32-bit Edition, versions 2.0, 2.1, 2.2,

         4.1, 4.2
    

SUMMARY

The 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 INFORMATION

To ensure that the Driver Manager and Cursor Library have the same cursor level:

  1. Open File Manager and go to the \WINDOWS\SYSTEM subdirectory.

  2. Highlight the file ODBC.DLL (or ODBC32.DLL) and press ALT+ENTER or choose Properties from the File menu.

  3. In the Version Information section of the dialog box that appears, select cursor level and note the level indicated.

  4. Follow steps 1 through 3 for the ODBCCURS.DLL (or ODBCCR32.DLL) file. If the cursor levels are not the same, the Driver Manager and Cursor Library do not match.

What to Do If the Driver Manager and Cursor Library Do Not Match

If 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
Keywords : kbenv MfcDatabase kbenv
Technology : kbMfc
Version : 1.5 1.51 1.52 2.0 2.1 2.2 4.1
Platform : NT WINDOWS
Issue type : kbhowto


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 26, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.