| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| MS Data Access Components (MDAC) (Spanish) - 32-Bit Win
| Product Summary |
Product: MS Data Access Components (MDAC)
Version: |
Category: Compliant*
Operating System: 32-Bit Win |
| Language: Spanish |
Release Date: N/A |
| Operational Range: |
- |
| Prerequisites: |
see below |
| Product Dependencies: |
Windows NT4 Service Pack 3 or higher, or Windows 9x operating systems. |
| Clock Dependencies: |
datetime data will correspond to the data source. |
| Last Updated: |
22 Jul 1999 | |
| Product Details |
|
Operational Range for Data: Dependent on Data Source (See Note D for more information)
Release Dates: 1997-1999
Prerequisites:
Updated MDAC version 2.0 or 2.1 (required Service Pack levels defined in table below),
Updated Microsoft Jet Database Engine (versions defined in table below),
Compliant versions of the following system components:
OLEAUT32.dll, (OLE/COM)
Msvcrt.dll, (runtimes from Visual C/C++,)
Expsrv.dll (Expression service from Visual Basic)
MFC40.dll (Microsoft Foundation Classes, from Visual C/C++)
WhatÆs new:
A separate Year 2000 compliance document is now available for the Microsoft Jet Database Engine.
The Microsoft Jet Database Engine statement contains updated information on Microsoft Jet compliance. Please review it for the latest information.
The latest release of MDAC is 2.1 sp2 (2.1.2.4202.3). The English (US) version is available for download on http:\\www.microsoft.com\data. Localized versions will be posted as they are completed. The initial languages should be posted within 60 days of English (US).
General information:
Microsoft Data Access Components (MDAC) is a collection of data connectivity components. This collection includes MDAC core components (ADO, RDS, OLE DB, ODBC), plus several OLE DB providers and ODBC drivers.
For customer convenience, the components are bundled together into a redistributable setup file, mdac_typ.exe. This setup is available through the web (at http://www.microsoft.com/data), and through various applications and products.
Separate year 2000 compliance documents have been made available for the core MDAC components, (ADO, RDS, OLE DB and ODBC). Known issues from those documents are already included in this summary. In addition, a year 2000 compliance document is now available for the Microsoft Jet Database Engine.
This MDAC document provides compliance information for MDAC releases, versions 1.5 through 2.1 Service Pack 2.
Version Localization:
Version 1.5: Brazilian, Chinese -Simplified, Chinese -Traditional, Czech, Danish, Dutch, English (US), Finnish, French, German, Greek, Hungarian, Italian, Japanese, Korean, Norwegian, Portuguese, Polish, Russian, Slovak, Slovenian, Spanish, Swedish, Turkish
Version 2.0 (with Visual Studio 6.0): Chinese -Simplified, Chinese -Traditional, English (US), French, German, Italian, Japanese, Korean, Spanish
Version 2.0 Service Pack 1 (with Windows NT 4 Service Pack 4):
Brazilian, Chinese -Simplified, Chinese ûTraditional, Czech, Danish, Dutch, English (US), Finnish, French, German, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Russian, Spanish, Swedish
Version 2.1 (with SQL Server 7.0 and 6.5 Service Pack 5): English (US), French, German, Japanese, Spanish
Version 2.1 Service Pack 1 (2.1.1.3711.6, shipped with Internet Explorer 5 only): Brazilian, Chinese -Simplified, Chinese ûTraditional, Czech, Danish, Dutch, English (US), French, Finnish, German, Greek, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese, Russian, Spanish, Swedish, Turkish, Basque, Icelandic
Version 2.1 Service Pack 1 (2.1.1.3711.11 Generally Available release):
Brazilian, Chinese (Simplified), Chinese (Traditional), Czech, Danish, Dutch, English (US), Finnish, French, German, Greek, Hungarian, Portuguese, Italian, Japanese, Korean, Norwegian, Polish, Russian, Spanish, Swedish, Turkish, Basque, Icelandic
Version 2.1 Service Pack 2 (2.1.2.4202.3 Generally Available release):
English (US) is available now, and the initial localized versions will be posted within 60 days.
The following table lists MDAC releases, compliance before remediation, and sources of remediation.
|
MDAC Release |
Year |
Compliance before remediation |
Component containing Year 2000 issues (details below ) |
Remediation alternatives |
|
1.5 |
1997 |
Compliant# |
Note A û OLE DB Data Coercion,
Note C û Microsoft Jet Database Engine |
Updated 1.5 dlls (msdadc.dll, msadce.dll) from Internet Explorer 4.01 Service Pack 2 or from Windows 98 year 2000 package
plus latest Microsoft Jet 3.5x.
See Microsoft Jet Database Engine Year 2000 statement for remediation download location
OR
MDAC 2.0 Service Pack 2: from http://www.microsoft.com/data
plus latest Microsoft Jet 3.5x.
See Microsoft Jet Database Engine Year 2000 statement for remediation download location.
OR
MDAC 2.1 Service Pack 1 (2.1.1.3711.11) :
Note: this version of MDAC includes Microsoft Jet4, not Jet 3.51. It will not overwrite your existing version of Microsoft Jet 3.51; instead it installs version 4 of Microsoft Jet.
OR
MDAC 2.1 Service Pack 2 (2.1.2.4202.3) :
from http://www.microsoft.com/data
Note: this version of MDAC includes Microsoft Jet4, not Jet 3.51. It will not overwrite your existing version of Microsoft Jet 3.51; instead it installs version 4 of Microsoft Jet.
|
|
2.0 |
1998 |
Compliant# |
Note A û OLE DB Data Coercion
Note B û SQL Server OLE DB provider
Note C û Jet |
MDAC 2.0 Service Pack 2: from http://www.microsoft.com/data
plus latest Microsoft Jet 3.5x.
See Microsoft Jet Database Engine Year 2000 statement for remediation download location.
OR
MDAC 2.1 Service Pack 1 (2.1.1.3711.11)
Note: this version of MDAC includes Microsoft Jet4, not Jet 3.51. It will not overwrite your existing version of Microsoft Jet 3.51; instead it installs version 4 of Microsoft Jet.
OR
MDAC 2.1 Service Pack 2 (2.1.2.4202.3) :
from http://www.microsoft.com/data
Note: this version of MDAC includes Microsoft Jet4, not Jet 3.51. It will not overwrite your existing version of Microsoft Jet 3.51; instead it installs version 4 of Microsoft Jet.
|
|
2.0 SP1 |
1998 |
Compliant# |
Note C û Jet |
Latest Microsoft Jet 3.5x.
See Microsoft Jet Database Engine Year 2000 statement for remediation download location. |
|
2.1 |
1998 |
Compliant# |
Note C - Jet |
Latest Microsoft Jet 4.0 which ships as part of MDAC 2.1 SP1 (2.1.1.3711.11) and MDAC 2.1 SP2 (2.1.2.4202.3)
http://www.microsoft.com/data |
|
2.0 SP2 |
1999 |
Compliant# |
Note C- Jet |
Latest Jet 3.5x.
See Microsoft Jet Database Engine Year 2000 statement for remediation download location. |
|
2.1 SP1, 3711.6 |
1999 |
Compliant |
|
No remediation needed.
Subset of 2.1 Service Pack 1, shipped with Internet Explorer 5 only. |
|
2.1 SP1, 2.1.1.3711.11 |
1999 |
Compliant |
|
No remediation needed.
(Note, this release is sometimes referred to as MDAC 2.1 Service Pack 1a.) |
|
2.1 SP2, 2.1.2.4202.3
|
1999 |
Compliant |
|
No remediation needed.
Release is available on http://www.microsoft.com/data
(Note, this release is sometimes referred to as MDAC 2.1 Service Pack 2.)
|
Note A (OLE DB compliance):
The known Year 2000 issues for OLE DB data coercion library are:
If you code to ADO,
AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp.
AND you are using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98)
AND you specify a two-digit year less than 60,
AND you do not specify a time as part of the date/time information
THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
If you code directly to OLE DB, the same case exists:
If you are converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as:
DBTYPE_DATE
DBTYPE_DBDATE
DBTYPE_DBTIME
DBTYPE_FILETIME
DBTYPE_DBTIMESTAMP
AND you are using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98)
AND you specify a two-digit year less than 60,
AND you do not specify a time as part of the date/time information
THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
Note B: SQL Server OLE DB provider compliance
The SQL Server OLE DB provider (sqloledb.dll) does not use the core OLE DB Data Coercion library. Instead, it implements its own data coercion module. This module has the same Year 2000 issues described in Note A. Specifically:
If you code to ADO,
AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp.
AND you are using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98)
AND you specify a 2-digit year less than 60,
AND you do not specify a time as part of the date/time information
THEN the SQL Server provider (sqloledb.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
If you code directly to OLE DB APIs, the same case exists:
If you are converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as:
DBTYPE_DATE
DBTYPE_DBDATE
DBTYPE_DBTIME
DBTYPE_FILETIME
DBTYPE_DBTIMESTAMP
AND you are using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98)
AND you specify a two-digit year less than 60,
AND you do not specify a time as part of the date/time information
THEN the SQL Server provider (sqloledb.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
Note C: Microsoft Jet Database Engine Compliance
See Microsoft Jet Database Engine Year 2000 document for the latest information, including download locations for remediation.
Note D: General information:
1) Common date usage errors:
Use 4-digit years when storing data or calling methods/properties of any of the MDAC data access Application programming interfaces (APIs). Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).
2) Testing guidelines and recommendations:
Since there is some "windowing" inherent in the year 2000 compliance features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.
3) Operational range and early dates:
If you're coding directly to OLE DB, and youÆre converting a Variant BSTR to DBDATE, the date "0001-01-01" (January 1, year 1) may be interpreted as "2001-01-01" (January 1, year 2001). This issue affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100.
How to determine which version of MDAC is installed, and whether you have compliant versions of OLE DB Data Coercion, Microsoft Jet Database Engine, and SQL Server OLE DB provider:
In general, to check the version of a file it is often easiest to use the Find (file) command in the Tools section of Explorer. After selecting the file, right clicking allows you to examine the Properties which includes a Version tab.
- For MDAC overall, the key files to check are msdadc.dll and oledb32.dll, which are used for the OLE DB data coercion library.
|
MDAC version |
Msdadc.dll version (for x86) |
Oledb32.dll version (for x86) |
DataCoercion compliance before remediation |
|
1.5 |
1.50.3506 |
None |
Compliant# |
|
1.5 remediated |
1.50.9801 |
None |
Compliant |
|
2.0 |
2.00.3002.4 |
2.00.1706 |
Compliant# |
|
2.0 SP1 |
2.00.3002.23 |
2.00.1706 |
Compliant |
|
2.0 SP2 |
2.00.3002.23 |
2.00.1706 |
Compliant |
|
2.1 |
2.10.3513.0 |
2.10.3513.0 |
Compliant |
|
2.1 SP1, 3711.6 (shipped with Internet Explorer 5 only) |
2.10.3711.2 |
2.10.3711.2 |
Compliant |
|
2.1 SP1, 3711.11 |
2.10.3711.2 |
2.10.3711.9 |
Compliant |
|
2.1 SP2, 2.1.2.4202.3 |
2.10.4202.0 |
2.10.4202.0 |
Compliant
|
***Please note, MDAC 2.0 SP2 is a super-set of MDAC 2.0 SP1. That is, MDAC 2.0 SP2 contains the MDAC components from 2.0 SP1, plus OLE DB providers for SQL Server and Oracle, and an updated oleaut32.dll.
2) Microsoft Jet Database Engine
Since Microsoft Jet can ship outside of MDAC, the Microsoft Jet version should be checked in addition to the MDAC version. See Microsoft Jet Database Engine Year 2000 document for the latest information on compliant versions and remediation alternatives.
- To confirm the version of the SQL Server OLE DB provider, check sqloledb.dll
|
SQL Server OLE DB provider version |
Compliance |
Shipped with MDAC version |
|
07.00.503 |
Compliant# |
MDAC 2.0 |
|
07.01.623 |
Compliant |
MDAC 2.0 Service Pack 2,
MDAC 2.1,
MDAC 2.1 Service Pack 1, 3711.11 |
|
07.01.690
|
Compliant |
MDAC 2.1 Service Pack 2, 2.1.2.4202.3 |
| |
Return to Search Screen
| Legend of Symbols: |
| * |
The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document. |
| # |
The product is compliant with an acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product. |
| + |
The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details. |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
If after reviewing this information you have additional questions related to this product, click here.
YEAR 2000 READINESS DISCLOSURE
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.
ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|
