FIX: You receive "Method Close of object _RecordSet failed" error message when you call the SQLGetInfo function with the SQL_CURSOR_COMMIT_BEHAVIOR attribute in Microsoft Data Access Components (MDAC) 2.8

This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
Consider the following scenario.
  • You have a Microsoft ActiveX Data Objects (ADO) based application.
  • You use the Microsoft OLE DB provider for ODBC.
  • The OLE DB provider for ODBC returns SQL_CB_DELETE when you call the SQLGetInfo function with a SQL_CURSOR_COMMIT_BEHAVIOR attribute.
When this occurs, you receive an error message that is similar to the following:
Method 'Close' of object '_RecordSet' failed.
RESOLUTION
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

None

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other software updates.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version         Size     File name   ---------------------------------------------------------   25-Mar-2005  16:16  2000.85.1060.0   73,728  Dbnetlib.dll        25-Mar-2005  16:17  2000.85.1060.0   28,672  Dbnmpntw.dll        25-Mar-2005  16:16  2.80.1060.0     315,392  Msadce.dll          25-Mar-2005  16:16  2.80.1060.0     135,168  Msadco.dll          25-Mar-2005  16:16  2.80.1060.0      49,152  Msadcs.dll          25-Mar-2005  16:16  2.80.1060.0     147,456  Msadds.dll          25-Mar-2005  16:16  2.80.1060.0     507,904  Msado15.dll         25-Mar-2005  16:17  2.80.1060.0     163,840  Msadomd.dll         25-Mar-2005  16:17  2.80.1060.0     184,320  Msadox.dll          25-Mar-2005  16:16  2.80.1060.0      53,248  Msadrh15.dll        25-Mar-2005  16:17  2.80.1060.0     225,280  Msdaora.dll         25-Mar-2005  16:16  2.80.1060.0     192,512  Msdaprst.dll        25-Mar-2005  16:16  2.80.1060.0     147,456  Msdart.dll          25-Mar-2005  16:16  2.80.1060.0     303,104  Msdasql.dll         25-Mar-2005  16:17  2.575.1060.0    139,264  Msorcl32.dll        25-Mar-2005  16:16  3.525.1060.0    221,184  Odbc32.dll          25-Mar-2005  16:17  2000.85.1060.0   24,576  Odbcbcp.dll         25-Mar-2005  16:16  2.80.1060.0     442,368  Oledb32.dll         25-Mar-2005  16:16  2000.85.1060.0  503,808  Sqloledb.dll        25-Mar-2005  16:16  2000.85.1060.0  401,408  Sqlsrv32.dll        25-Mar-2005  03:16  2000.85.1060.0  208,896  Sqlxmlx.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION

Steps to reproduce the problem

  1. Make sure that you install an ODBC driver that supports the SQL_CB_DELETE return value on the test computer.
  2. Create a Data Source Name (DSN) that is named DSNName on the computer.
  3. Use the following code to produce the error message that is mentioned in the "Symptoms" section:
    Dim conn As ADODB.ConnectionSet conn = New ADODB.Connectionconn.Open "DSN=DSNName"sql = "select * from TableName"Set rs = New ADODB.Recordsetconn.BeginTransrs.Open sql, connrs.MoveFirstconn.CommitTransrs.Close '<---- The error occurs here.conn.CloseSet rs = NothingSet conn = Nothing
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
839801 FIX: Hotfixes are available for MDAC 2.8
824684 Description of the standard terminology that is used to describe Microsoft software updates
Properties

Article ID: 895485 - Last Review: 01/17/2015 10:15:29 - Revision: 1.5

Microsoft Data Access Components 2.8

  • kbnosurvey kbarchive kbautohotfix kbfix kbbug kbhotfixserver kbqfe KB895485
Feedback