MDAC is included with Microsoft SQL Server, Microsoft Visual Studio, Microsoft Office, Microsoft Back Office, and other Microsoft products. Additionally, you can redistribute the MDAC stack through the MDAC_TYP.exe file. To download MDAC_TYP.exe, visit the following Microsoft Web site: NoteMicrosoft recommends that you first test your application with MDAC 2.8 in a test environment to make sure that you are aware of any compatibility issues before you decide to use or to upgrade to MDAC 2.8
With so many recent MDAC releases, applications have experienced version incompatibility issues under certain circumstances. This is dependent on the environment where MDAC was installed. In most scenarios, applications that experience problems with MDAC are a result of mismatched components
Note Removing or replacing some of the MDAC components from the operating system can cause data loss and unpredictable results. MDAC components are system components; they are installed as part of the operating system on computers that are running Windows Millennium Edition, Windows 2000, and later versions of Windows. Therefore, you cannot manually modify or remove MDAC from these operating systems.
- Perform an analysis of your machine and automatically determine the release version.
- Perform an analysis against a selected version.
- Scan the machine. Don't perform an analysis.
When you run the second option to select a specific MDAC version, you receive an analysis that is run against this specific version with the following information:
- File details
- COM details
- Registry details
After the analysis is run for the selected MDAC version, each of these entries on the left pane contains one of the following subentries:
- Not Found
The Match subentry includes all details about all MDAC components and registry entries that are matched to the selected MDAC version.
The Mismatch subentry includes entries for components and registry entries that exist in the current selected MDAC version, but where a mismatch was found. Typically, these are the components that you must investigate when you suspect that there are any MDAC installation or configuration issues.
The Not Found subentry refers to components or registry keys that are not found (do not exist) in the selected MDAC version. Therefore, it cannot compare these components or registry keys to verify if there is a match or a mismatch. Typically, these can be older components that may have been discontinued in later MDAC versions or may be newer versions that did not exist in older MDAC versions.
The ComCheck.chm Help file in the \ComCheck folder provides more detailed information about the user interface and other functions.
To save an analysis for the MDAC components that are installed on your computer, click Save on the File menu. This saves the output as an XML file in any location that you specify on your computer.
Article ID: 307255 - Last Review: Jul 10, 2012 - Revision: 1