Release manifest for MDAC 2.6 (2.60.6526.3)

Article translations Article translations
Article ID: 842272 - View products that this article applies to.
Expand all | Collapse all

On This Page

Summary

This article describes the release manifest of Microsoft Data Access Components (MDAC) 2.6 and includes the following information about MDAC 2.6:
  • The minimum configuration requirements for MDAC 2.6.
  • The frequently asked questions about MDAC 2.6.
  • The known issues with MDAC 2.6.
  • The significant fixes for MDAC 2.6.
  • The list of files that are included in MDAC 2.6 and the versions of these files.

INTRODUCTION

This release manifest applies to the Internet release of MDAC 2.6 (2.60.6526.3). This release manifest lists frequently asked questions about MDAC 2.6 and describes known issues with MDAC 2.6. This release manifest also lists all the files that are included in MDAC 2.6, and this manifest lists the corresponding versions of these files.

For more information about installing, removing, upgrading, and downgrading MDAC releases, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms810805.aspx
For more information about downloading MDAC releases, visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx

More information

Release version number

MDAC 2.6 (2.60.6526.3), September 2000

Release function

This release provides, directly to the public, the same version of MDAC that is included with Microsoft SQL Server 2000.

Release ship vehicle

To download MDAC 2.6 (2.60.6526.3), visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/data/aa937695.aspx

Localization information

MDAC 2.6 (2.60.6526.3) is available in the following languages:
  • U.S. English
  • Czech
  • Danish
  • Dutch
  • Finnish
  • Greek
  • Hungarian
  • Norwegian
  • Polish
  • Portuguese (Brazil)
  • Portuguese
  • Russian
  • Slovak
  • Slovenian
  • Swedish
  • Turkish

Minimum supported configuration

The following list describes the minimum supported configurations for MDAC 2.6 (2.60.6526.3):
  • Microsoft Windows 95 with the Year 2000 Update and Microsoft Internet Explorer 4.01 Service Pack 2 (SP2) or later
  • Microsoft Windows 98 with Year 2000 Update 2 and Internet Explorer 4.01 SP2 or later
  • Microsoft Windows 98 Second Edition
  • Microsoft Windows Millennium Edition (Me)
  • Microsoft Windows NT 4.0 Service Pack 5 (SP5) or later and Internet Explorer 4.01 SP2 or later
  • Microsoft Windows 2000

New features

This release extends Microsoft OLE DB and Microsoft ActiveX Data Objects (ADO) to expose the XML features of Microsoft SQL Server 2000. These features include the following:
  • Support for result sets as Stream objects.
  • The ability to use a Stream object as the input for a Command object.
This release also offers the following:
  • Enhanced support for singleton SELECT statements in Microsoft OLE DB Provider for SQL Server (SQLOLEDB) and ADO.
  • Enhanced ADO error reporting.
  • Retrieval of schema objects by Microsoft ActiveX Data Objects (Multidimensional) (ADO MD) users without instantiating and walking the CubeDef object's hierarchy.
Additionally, this release has a more robust redistributable setup that includes the following:
  • Files-in-use checking that prompts the user to shut down applications that use MDAC features before the MDAC installation begins. When the user uses this feature, the user does not have to restart the computer after the installation is complete.
  • Support for rolling back MDAC 2.6.

Frequently asked questions about MDAC 2.6

Q1: Where can I find specific Microsoft Knowledge Base (KB) articles for MDAC 2.6?

A1: You can search the public Knowledge Base and use the kbmdac260 keyword.

Note You must only search the Microsoft Knowledge Base for specific technical information, not for bug-related issues. Many bug-related articles describe either fixed bugs or known bugs in this version of the product.

To search the Knowledge Base, visit the following Microsoft Web site:
http://support.microsoft.com
Q2: Where can I find more information about how to set up MDAC, including information about dependencies, supported operating systems, and rollback?

A2: For more information about these topics, visit the following Microsoft Web site:
http://support.microsoft.com/kb/842193/en-us
Q3: My application requires Microsoft Jet, but Jet is no longer included in MDAC. Where can I obtain Jet?

A3: MDAC versions 2.6 and later do not include Microsoft Jet. For additional information about the issues involving Jet, click the following article number to view the article in the Microsoft Knowledge Base:
271908 INFO: MDAC version 2.6 and later do not contain Jet or Desktop ODBC drivers
Q4: My application requires the Microsoft Visual FoxPro ODBC driver, but this driver is not included in MDAC 2.6. Where can I obtain the Microsoft Visual FoxPro ODBC driver?

A4: The Visual Fox Pro ODBC driver is included in Visual FoxPro, Microsoft Windows 2000, Microsoft Office 2000, and MDAC 2.5.

Q5: Do all providers support the Record object?

A5: No. Currently, only the Microsoft OLE DB Provider for Internet Publishing, Microsoft Exchange 2000, and Microsoft OLE DB Provider for SQL Server support the Record object.

Q6: Can ADO consume any format of XML?

A6: No. Currently, the Recordset object can only be created from XML that is formatted in the adPersistXML format.

Q7: I am having trouble connecting to my Oracle server. Where can I find more information about how to configure my computer?

A7: For additional information about how to register Oracle Call Interface (OCI) version issues, click the following article number to view the article in the Microsoft Knowledge Base:
193893 Using Oracle with Microsoft Transaction Server and COM+

Known issues with MDAC 2.6 (2.60.6526.3)

This MDAC release has the following known issues.

MDAC

  • The default network library for connecting to the computer that is running SQL Server has changed from Named Pipes to TCP/IP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
    289573 PRB: Configuring DSNs with SQL Server Net-Libraries
  • If a clustered server is running SQL Server 6.5 or SQL Server 7.0, connectivity problems occur in the cluster if you install MDAC 2.6 on that server. There is no workaround. Do not install MDAC 2.6 if the clustered server is running SQL Server 6.5 or SQL Server 7.0.
  • When you create or configure ODBC Data Source Names (DSNs) by using the Microsoft SQL Server ODBC driver, the following issues may occur:
    • Net-Library protocols are switched.
    • The protocol of a new data source name (DSN) is used for older DSNs or vice versa.
    For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
    289573 PRB: Configuring DSNs with SQL Server Net-Libraries

ADO

  • When you use ADO 2.6 with the Exchange 2000 OLE DB provider, an error occurs when you call the Recordset.MoveNext method. To work around this issue, use the Recordset.Move(1, adBookmarkCurrent) method. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
    273791 MDAC 2.6 breaks ADO MoveNext() function with Exchange 2000
  • ADO 2.6 does not return provider-specific error descriptions from the Exchange 2000 OLE DB provider. The user receives an "automation error" description instead of the detailed description that the provider provides.
  • Microsoft OLE DB Provider for ODBC can cause a memory leak when Microsoft OLE DB Provider for ODBC is used in script or with Microsoft Visual Basic. When ODBC returns a warning message, the memory that is allocated for the ERRORINFO structure is not released. A warning message may be returned for several reasons. For example, a warning message may be returned when the application selects a cursor type that the underlying ODBC driver does not support. This leak also occurs in earlier MDAC versions. To avoid the leak, you can modify the code so that warnings are not produced, or you can use a different OLE DB provider.
  • Certain Borland ADOExpress applications generate the following error message when the applications run against MDAC 2.6:
    Either EOF or BOF is True, or the current record has been deleted. Requested operation requires a current record.
     Generally, this error occurs when you close an empty data set. The same error may also occur when you cancel an edit operation. To correct this error, you must recompile the application by using the updated ADOExpress units that are available from Borland.

SQL Server ODBC Driver

  • When ODBC uses a connection that is marked as Using SQLServer Server authentication and the server is not in a trusted domain, the user receives a "failed to connect" error message that indicates that an attempted integrated security logon was not successful. After the user closes this message, the user is prompted to type a SQL Server user ID and password, and then the user can connect as expected.

XML

  • The Msxml2.dll file does not register correctly on a 32-processor computer when you install MDAC 2.6. There is no workaround.

Significant fixes for MDAC 2.6 (2.60.6526.3)

The following significant fixes were implemented in this MDAC release:

The ADO Find and Filter methods must include a way to escape embedded single quotation marks in string literals.

Because you cannot control what a user types when the user builds a filter, the ADO Find method the ADO Filter method must include a way to escape the single quotation mark (') if the user types it. The user can escape this delimiter by typing the single quotation mark (') two times in a row when the user builds a filter. For example, a user can type the string "O''Brien" to find "O'Brien."

When you use a parameterized Command object, the connection is not released when you disconnect a Recordset object and close a connection.

If you open a Recordset object from a parameterized Command object, and then you disconnect that Recordset object from the connection, the physical connection to the database does not close until the process ends or until the Recordset object is closed. Therefore, connections are not released, and the maximum number of connections may be exceeded and performance may decrease. With this MDAC release, the physical connection closes correctly.

When you use SQLOLEDB, you cannot add a default value for a column by using Microsoft ActiveX Data Objects Extensions for Data Definition Language and Security (ADOX).

When you try to add a default value to a column, you receive the following error message from ADO:
Application uses a value of the wrong type for the current operation.
This problem occurs because ADOX tries unsuccessfully to convert the value to a variant. However, because the coercion code has been removed from this release, ADOX now successfully passes the default value directly to the provider.

You cannot refresh the Members collection in ADO MD.

After you populate the Members collection in ADO MD, modify the members of the cube in the OLAP database, and call the Refresh method of the Members collection, the Members collection may not reflect the changes that were made to the members of the cube. This release fixes this issue. In this release, ADO MD queries the OLAP database again instead of reloading the Members collection with data that ADO MD previously cached.

File list for MDAC 2.6 (2.60.6526.3)

Collapse this tableExpand this table
File nameVersion (x86)Description
12520437.cpxSQL Server code page translator
12520850.cpxSQL Server code page translator
Adcjavas.incADC/RDS JavaScript include file
Adcvbs.incADC/RDS VBScript include file
Adojavas.inc ADO JavaScript include file
Adovbs.incADO VBScript include file
Advpack.dll5.50.4134.600Advanced .inf installer
Cabinet.dll1.0.603.0
Cliconf.chmSQL Server client configuration Help file
Cliconfg.dll2000.80.194.0Client configuration utility
Cliconfg.exe2000.80.194.0Client configuration utility
Cliconfg.rll2000.80.194.0Client configuration utility
Dbmsadsn.dll2000.80.194.0Pipes Net DLL for SQL clients
Dbmsgnet.dll2000.80.194.0
Dbmsrpcn.dll2000.80.194.0RPC Net-Library
Dbmsvinn.dll 2000.80.194.0VINES Net-Library
Dbnetlib.dll 2000.80.194.0Winsock oriented Net DLL for SQL clients
Dbnmpntw.dll 2000.80.194.0Pipes Net DLL for SQL clients
Ds16gt.dll3.510.3711.0ODBC 16-bit driver setup generic thunking
Ds32gt.dll3.520.6526.0Data Access - ODBC driver setup generic thunking
Expsrv.dll6.0.0.8540Basic for Applications Runtime - expression service
Handler.regRegistration entries file for setting up the default RDS handler
Handsafe.regRegistration entries file for making RDS always run with a safe handler
Handunsf.regRegistration entries file for making RDS not require a safe handler
Instcat.sqlSQL Server stored procedure catalog updater
Msadce.dll2.60.6526.0Data Access - OLE DB cursor engine
Msadcer.dll2.60.6526.0Data Access - OLE DB cursor engine resources
Msadcf.dll2.60.6526.0Data Access - Remote Data Services data factory
Msadcfr.dll
Msadco.dll2.60.6526.0Data Access - Remote Data Services data control
Msadcor.dll2.60.6526.0Data Access - Remote Data Services data control resources
Msadcs.dll2.60.6526.0Data Access - Remote Data Services ISAPI library
Msadds.dll2.60.6526.0Data Access - OLE DB data shape provider
Msaddsr.dll2.60.6526.0Data Access - OLE DB data shape provider resources
Msader15.dll2.60.6526.0Data Access - ADO resources
Msado15.dll2.60.6526.0Data Access - ADO
Msado20.tlb2.60.6526.0Data Access - ADO 2.0 type library
Msado21.tlb2.60.6526.0Data Access - ADO 2.1 type library
Msado25.tlb2.60.6526.0Data Access - ADO 2.5 type library
Msadomd.dll2.60.6526.0Data Access - ADO MD
Msador15.dll2.60.6526.0Data Access - ADO
Msadox.dll2.60.6526.0Data Access - ADO extensions
Msadrh15.dll2.60.6526.0Data Access - ADO rowset helper
Mscpx32r.dll3.511.320.0
Mscpxl32.dll3.511.3.20ODBC code page translator
Msdadc.dll2.60.6526.0Data Access - OLE DB data conversion stub
Msdaenum.dll2.60.6526.0Data Access - OLE DB root enumerator stub
Msdaer.dll2.60.6526.0Data Access - OLE DB error collection stub
Msdamg9x.dll2.60.6526.3Data Access - Windows 98 migration DLL
Msdaora.dll2.60.6526.0Data Access - OLE DB Provider for Oracle
Msdaorar.dll2.60.6526.0
Msdaosp.dll2.60.6526.0Data Access - OLE DB simple provider
Msdaprsr.dll2.60.6526.0Data Access - OLE DB persistence services resources
Msdaprst.dll2.60.6526.0Data Access - OLE DB persistence services
Msdaps.dll2.60.6526.0Data Access - OLE DB interface proxies/stubs
Msdarem.dll2.60.6526.0Data Access - OLE DB remote provider
Msdaremr.dll2.60.6526.0Data Access - OLE DB remote provider resources
Msdart.dll2.60.6526.0
Msdasc.chmOLE DB service components HTML Help file
Msdasc.dll2.60.6526.0Data Access - OLE DB service components stub
Msdasql.dll2.60.6526.0Data Access - OLE DB provider for ODBC drivers
Msdasqlr.dll2.60.6526.0Data Access - OLE DB provider for ODBC drivers resources
Msdatl3.dll2.60.6526.0Data Access - OLE DB implementation support routines
Msdatsrc.tlb9.0.6526.0Data Access - data source interfaces
Msdatt.dll2.60.6526.0Data Access - OLE DB temporary table services
Msdaurl.dll9.1.6526.0Data Access - OLE DB RootBinder stub
Msdfmap.dll2.60.6526.0Data Access - data factory handler
Msdfmap.iniInitialization file for configuring the default RDS handler
Msjro.dll2.60.6526.0Jet and replication objects
Msjtes40.dll4.0.2927.8Jet expression service
Msorc32r.dll2.60.6526.0
Msorcl32.chmOracle ODBC driver Help file (compiled HTML)
Msorcl32.dll2.573.6526.0Data Access - ODBC Driver for Oracle
Msvcirt.dll6.0.8168.0C++ runtime library
Msvcrt.dll6.0.8397.0C runtime library
Mswdat10.dll4.0.3829.2Jet sort tables
Mswstr10.dll4.0.3829.2Jet sort library
Msxactps.dll2.60.6526.0Data Access - OLE DB transaction proxies/stubs
Msxml2.dll8.0.6518.2
Msxml2a.dll8.0.6518.2Microsoft XML parser resource library
Msxml2r.dll8.0.6518.2Microsoft XML parser resource library
Mtxdm.dll1999.6.902.0MTS connection pooling - ODBC driver manager
Mtxoci.dll1999.6.854.0MTS - Oracle OCI
Odbc16gt.dll3.510.3711.0ODBC 16-bit generic thunking
Odbc32.dll3.520.6526.0Data Access - ODBC driver manager
Odbc32gt.dll3.520.6526.0Data Access - ODBC driver generic thunking
Odbcad32.exe3.520.6526.0Data Access - ODBC administrator
Odbcbcp.dll2000.80.194.0SQL Server ODBC driver BCP library
Odbcconf.dll3.520.6526.3Data Access - ODBC driver configuration program
Odbcconf.exe3.520.6526.3Data Access - ODBC driver configuration program
Odbcconf.rspData Access - ODBC driver configuration file
Odbccp32.cpl3.520.6526.0Data Access - ODBC control panel
Odbccp32.dll3.520.6526.0Data Access - ODBC installer
Odbccr32.dll3.520.6526.0Data Access - ODBC cursor library
Odbccu32.dll3.520.6526.0Data Access - ODBC cursor library
Odbcinst.chmODBC HTML help
Odbcint.dll3.520.6526.0Data Access - ODBC resources
Odbcp32r.dll3.520.6526.0
Odbctrac.dll3.520.6526.0Data Access - ODBC driver manager trace
Oledb32.dll2.60.6526.0Data Access - OLE DB core services
Oledb32a.dll2.60.6526.0
Oledb32r.dll2.60.6526.0Data Access - OLE DB core services resources
Oledb32x.dll2.60.6526.0Data Access - OLE DB extensions
Oledbjvs.incOLE DB JavaScript include file
Oledbvbs.incOLE DB VBScript include file
Psapi.dll4.0.1371.1
Sqloledb.dll2000.80.194.0OLE DB Provider for SQL Server
Sqloledb.rll2000.80.194.0OLE DB Provider for SQL Server resource library
Sqlsodbc.chmSQL Server ODBC Help
Sqlsoldb.chmSQL Server OLEDB Help
Sqlsrv32.dll2000.80.194.0SQL Server ODBC driver
Sqlsrv32.rll2000.80.194.0SQL Server ODBC driver resource library
Sqlunirl.dll2000.80.194.0SQL Server Unicode resource layer library
Sqlxmlx.dll2000.80.194.0
Sqlxmlx.rll2000.80.194.0OLE 2.40 for Windows NT and Windows 95 operating systems
Vbajet32.dll6.0.1.8268Visual Basic for Applications development environment - expression service loader

References

For more information about product downloads and update downloads, visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/data/aa937712.aspx

Properties

Article ID: 842272 - Last Review: June 6, 2013 - Revision: 5.0
Applies to
  • Microsoft Data Access Components 2.6
Keywords: 
kbhowto kbinfo KB842272

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com