Article ID: 842279 - View products that this article applies to.
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows Registry
This article discusses the release manifest of Microsoft Data Access Components (MDAC) 2.1. This article includes the following details about MDAC 2.1:
This release manifest applies to the Internet release of the first generally available (GA) version of MDAC 2.1 (188.8.131.5211.11). This version is also known as MDAC 184.108.40.20611.11 (GA). This release manifest lists frequently asked questions about MDAC 220.127.116.1111.11 (GA). This release manifest describes known issues with MDAC 18.104.22.16811.11 (GA). This release manifest lists all the files that are included in MDAC 22.214.171.12411.11 (GA). This release manifest also lists the corresponding versions of these files.
For more information about installing, uninstalling, upgrading, and downgrading MDAC releases, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms810805.aspxFor more information about downloading MDAC releases, visit the following MSDN Web site:
Release version numberMDAC 126.96.36.19911.11 (GA), April 1999
Release functionThis release provides the same version of MDAC that is included with Microsoft Office 2000 directly to the public.
Release ship vehicleTo download MDAC 188.8.131.5211.11 (GA), visit the following MSDN Web site:
Localization informationMDAC 184.108.40.20611.11 (GA) is currently available in the following languages:
New featuresThere are no new features in this release.
Known issues for MDAC 220.127.116.1111.11 (GA)The following is a summary of known issues with the MDAC 18.104.22.16811.11 (GA) release. Information is provided about known issues that include the following:
Issue with the Jet database engineMDAC 22.214.171.12411.11 (GA) contains Jet 4.0 Service Pack 1 (SP1). The version number for Jet 4.0 SP1 is 4.0.2521.08. This version of Jet is the same as the version that is included with Microsoft Office 2000. This release is a generally available release of Jet. The initial version of Jet 4.0, version 4.0.2115.25, is included in MDAC 2.1. MDAC 2.1 is released with Microsoft SQL Server 7.0. MDAC 2.1 is targeted specifically for internal use by SQL Server 7.0. Jet 4.0 SP1 contains many significant improvements over Jet 4.0 (4.0.2115.25).
For more information about data access and storage downloads, visit the following Microsoft Web site:
Issue with Jet 4.0 and the MDAC Access ODBC driverWhen you install MDAC 126.96.36.19911.11 (GA), a new version of the Access ODBC driver, Odbcjt32.dll, is installed. This driver has the same file name as the MDAC 2.0 (Jet 3.5) driver. Therefore, ODBC Jet 3.5x applications are automatically upgraded to Jet 4.0 after you install MDAC 188.8.131.5211.11 (GA). This upgrade causes issues with Jet databases, with dBaseASE tables, and with Paradox tables.
Jet databasesIf the Jet database, or .mdb file, remains in a version 3.5 format after you install MDAC 184.108.40.20611.11 (GA), and the version is not compacted or converted to Jet 4.0, an ODBC application may experience performance degradation. The version Jet 4.0 database engine must load the Jet 3.5 database engine to access a database that was built by using Jet 3.5. Additionally, another process converts string data to and from ANSI and Unicode. Therefore, we recommend that you convert Jet 3.5 databases to Jet 4.0 databases.
Note Concurrent users of Jet 3.5 cannot open the database after it is converted.
dBaseASE tables and Paradox tablesIn versions of Jet 4.0 that are earlier than Jet 4.0, the I-ISAM drivers that access dBASE files and Paradox files experience problems with consistently maintaining indexes. Additionally, the I-ISAM drivers do not provide much support for ongoing, newer versions of these products and their file formats. Therefore, the Access ODBC Driver is upgraded to use the Borland Database Engine (BDE). The BDE is a product of InterBase. InterBase is a subsidiary of Inprise.
Users must know about certain behavior that occurs with the BDE and without the BDE:
Issue with Jet I-ISAM files and FoxProMicrosoft FoxPro file access does not exist in dBASE Installable Indexed Sequential Access Method (I-ISAM). Because you must directly access FoxPro data through the Microsoft FoxPro ODBC driver, a single, functionally consistent path of FoxPro data files through ODBC exists. You cannot access FoxPro tables through the Access ODBC driver and xBase I-ISAM. You must create a direct ODBC data source name (DSN) to the FoxPro ODBC driver, and then you must re-create your connections. The FoxPro ODBC driver handles FoxPro indexes correctly and supports all new FoxPro file formats.
Issue with Text I-ISAM filesWarning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
By default, Text I-ISAM exports to the ANSI code page in Jet 4.0. In Jet 3.5, Text I-ISAM exports to the OEM code page. If you want the default code page to be any other code page, you must modify the following registry entry:
Valid values for this key include the following:
Issue with the Access ODBC driver and dynamic cursorsWhen you use the Access ODBC driver, and then you request a dynamic cursor type, the row pointer is positioned in a random row or beyond the membership of the cursor if you delete a row and then perform a MoveNext operation. This behavior can prevent an application from correctly enumerating a cursor. This behavior can also prevent the application from accessing or deleting a row that was in the original rowset. A hotfix is available for this issue. We recommend that you build or use applications that use the Access ODBC driver for any version of MDAC 2.1.
For more information about data access and storage downloads, visit the following Microsoft Web site:
Issue with OLE DB Provider for JetWhen you use the OLE DB Provider for Jet 4.0 and an ADO server-side cursor that is bound to a DataGrid object, either through an ADO DataControl control or directly to the grid, the data may not be displayed in the DataGrid object.
To resolve this error, set the IRowsetIdentity property of the recordset to True before you open the recordset. For example, you can use the following code:
You can also work around this behavior. OLE DB Provider for Jet does not support the DBPROP_LITERALIDENTITY property. Therefore, this provider must implement the IRowsetIdentity interface. ADO must set this property before the rowset is opened. If you query for an interface such as the IRowsetIdentity interface, but OLE DB does not open the rowset to support this interface, you receive the E_NOINTERFACE error message even if the provider supports the interface.
Issue with Terminal ServerWhen you install the MDAC 2.1 redistributable components on a computer that is running Microsoft Terminal Server, the access control lists (ACLs) are changed on all files that MDAC installs in the System32 folder. Before you install the MDAC 2.1 redistributable components, everyone has Read access. However, after you install the MDAC 2.1 redistributable components, the user who just installed MDAC has Full Control access, and no other users have access.
To correct this problem, you can download the Mdac.txt batch file. This file is used to complete the installation of MDAC on a Microsoft Windows NT 4.0 Terminal Server computer.
After you install MDAC 220.127.116.1111.11 (GA), copy the Mdac.txt file to the System32 folder on your computer, and then rename the Mdac.txt file as Mdac.cmd. You can run the renamed file at the command prompt. To this, click Start, click Run, type system32\mdac.cmd, and then click OK.
For more information about the Mdac.txt batch file, visit the following Microsoft Web site:
Significant fixesThe following is a summary of known issues and significant fixes that are incorporated in the MDAC 18.104.22.16811.11 (GA) release.
These fixes are specific to MDAC and to Microsoft Access 2000, Microsoft Outlook 98, Microsoft Outlook 2000, and Microsoft Office Web services.
General fixesThe initial release of Internet Explorer 5 (build 5.00.2014.0216) contains MDAC 22.214.171.12411.6 (IE5). This release of Internet Explorer 5 may generate an application violation when an ADO consumer application tries to connect to a data source, or when you try to test a connection by using the Microsoft Data Links API. Specifically, this issue affects those OLE DB providers that do not have the optional OLEDB_SERVICES registry entry. This issue adversely affects Microsoft OLE DB Provider for DB2 and Microsoft OLE DB Provider for AS/400 and Virtual Storage Access Method (VSAM). This problem is resolved in Internet Explorer 5 build 5.00.2314.1003 and in MDAC 126.96.36.19911.11 (GA).
Backward compatibility fixesSignificant fixes were implemented in this release of MDAC. This release also includes fixes that are specific to MDAC and Access 2000, to Outlook 98, to Outlook 2000, and to Office Web services. The following fixes involve backward compatibility with MDAC 2.1:
Fixes for incompatibility and installation problemsThe following problems have been resolved:
File list for MDAC 188.8.131.5211.11 (GA) April 1999
Collapse this tableExpand this table
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
232060For more information about MDAC support, including information about ADO, OLEDB, ODBC, visit the following Microsoft Web site:
(http://support.microsoft.com/kb/232060/ )MDAC setup troubleshooting guide
http://support.microsoft.com/default.aspx?scid=fh;[LN];mdacFor more information about product downloads and update downloads, visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/data/aa937712.aspxThe third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.