Microsoft KB Archive/320778

= INFO: Explanation of the MDAC 2.7 Refresh Release =

Article ID: 320778

Article Last Modified on 5/17/2007

-

APPLIES TO


 * Microsoft Data Access Components 2.7

-



This article was previously published under Q320778



SUMMARY
The previously released download for MDAC 2.7 has been replaced with the MDAC 2.7 Refresh. Although no code changes have been made to the components in the MDAC 2.7 Refresh from MDAC 2.7, the MDAC 2.7 Refresh contains changes to the way the builds are organized and versioned, which corrects existing issues with the MDAC 2.7 installation. The most important change to remember when you install the MDAC 2.7 Refresh is that the version numbers of most components in the stack have been changed, as described in this article.



MORE INFORMATION
The MDAC 2.7 Refresh has been released primarily to address the issue that is described in the following Microsoft Knowledge Base article:

314755 BUG: Error When You Install MDAC 2.7 After MDAC 2.6 SP2

Because no coding changes have been made to any of the MDAC components from MDAC 2.7 to the MDAC 2.7 Refresh, a program that is tested against MDAC 2.7 should function and perform identically to a program that is tested against the MDAC 2.7 Refresh.

The primary change in the MDAC 2.7 Refresh is that the version numbers of most of the files that are included with MDAC have been updated. MDAC components are versioned in four parts, as follows:

[major version number].[minor version number].[build number].[revision]

For MDAC 2.7, the major version number is 2 and the minor version number is 70. These numbers are the same in the MDAC 2.7 Refresh. However, the build number for most files is now 9001, and the revision number is 0. Therefore, most of the files in the MDAC 2.7 Refresh have the following full versioning:

2.70.9001.0.

The files affected by these changes are those that are made up of the MDAC core as follows:
 * Open Database Connectivity (ODBC)
 * OLE DB
 * ActiveX Data Objects (ADO)
 * All Microsoft SQL Server interfaces, including the following:
 * Network libraries
 * ODBC driver
 * OLE DB provider

