Release manifest for MDAC 2.6 (2.60.6526.3)

• 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.

Back to the top

Release version number

Back to the top

Release function

Back to the top

Release ship vehicle

Back to the top

Localization information

• U.S. English
• Czech
• Danish
• Dutch
• Finnish
• Greek
• Hungarian
• Norwegian
• Polish
• Portuguese (Brazil)
• Portuguese
• Russian
• Slovak
• Slovenian
• Swedish
• Turkish

Back to the top

Minimum supported configuration

• 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

Back to the top

New features

• Support for result sets as Stream objects.
• The ability to use a Stream object as the input for a Command object.

• 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.

• 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.

Back to the top

Frequently asked questions about MDAC 2.6

Back to the top

Known issues with MDAC 2.6 (2.60.6526.3)

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  (http://support.microsoft.com/kb/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  (http://support.microsoft.com/kb/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  (http://support.microsoft.com/kb/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. For additional information, visit the following Web site:
  http://www.borland.com/devsupport/delphi/ (http://www.borland.com/devsupport/delphi/)
  Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

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.

Back to the top

Significant fixes for MDAC 2.6 (2.60.6526.3)

Back to the top

File list for MDAC 2.6 (2.60.6526.3)

Back to the top