Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

How to make sure that the ODBC.DLL and the ODBCCURS.DLL have the same cursor level in Visual C++


View products that this article applies to.

This article was previously published under Q127734

↑ Back to the top


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.

↑ Back to the top


More information

To make sure 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 version of Microsoft Data Access Components (MDAC) from the following Microsoft Web site: If the cursor level for the Driver Manager and Cursor Library do match, but the trace message listed earlier in this section still appears in the output, check to make sure that an older version of the DLLs are not anywhere in the path of the program. You can also use the Component Checker Utility to verify MDAC installation. For more information on Component Checker, click the following article number to view the article in the Microsoft Knowledge Base:
307255� Component Checker: Diagnose problems and reconfigure MDAC installations

↑ Back to the top


Keywords: kbinfo, kbdatabase, kbenv, kbhowto, KB127734

↑ Back to the top

Article Info
Article ID : 127734
Revision : 7
Created on : 11/21/2006
Published on : 11/21/2006
Exists online : False
Views : 475