Microsoft KB Archive/842272

= Release manifest for MDAC 2.6 (2.60.6526.3) =

Article ID: 842272

Article Last Modified on 3/20/2007

-

APPLIES TO


 * Microsoft Data Access Components 2.6

-



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



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

</li> 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.</li> 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.</li> The protocol of a new data source name (DSN) is used for older DSNs or vice versa.</li></ul>

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

</li></ul>

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

</li> ADO 2.6 does not return provider-specific error descriptions from the Exchange 2000 OLE DB provider. The user receives an &quot;automation error&quot; description instead of the detailed description that the provider provides.</li> 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.</li> 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/

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.</li></ul>

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 &quot;failed to connect&quot; 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 &quot;O''Brien&quot; to find &quot;O'Brien.&quot;

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)
<div class="references_section">