| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Microsoft OLE DB 1.5 (Polish) - 32-Bit Win
| Product Summary |
Product: Microsoft OLE DB
Version: 1.5 |
Category: Compliant*#
Operating System: 32-Bit Win |
| Language: Polish |
Release Date: N/A |
| Operational Range: |
- |
| Prerequisites: |
Windows NT4 Service Pack 3 or higher, or Windows 9x operating systems |
| Product Dependencies: |
OLEAUT32, COM, msvcrt.dll, |
| Clock Dependencies: |
None except that datetime data will always correspond to the data source. |
| Last Updated: |
19 May 1999 | |
| Product Details |
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below.
Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through
Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4
Microsoft Data Access Components (MDAC) 2.1
See Note 2 below for more information.
How the product handles dates:
The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME.
Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings.
DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts.
Two-digit shortcut handling:
OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX.
Common date usage errors:
Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access 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).
Testing guidelines and recommendations:
Since there is some "windowing" inherent in the date 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.
Known issues:
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're 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 year less than 60,
THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
OR,
If you code directly to OLE DB, the same case exists:
If you're 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're 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 year less than 60,
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 1:
If you're coding directly to OLE DB, and youÆre converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100.
NOTE 2:
To distinguish a compliant version of OLE DB from one thatÆs Compliant#:
1) check the version of the DLL pointed to by this registry key:
HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default)
2) OLE DB is Compliant# if the version is
greater than 1.50.0000 and less than 1.50.9801, or
greater than 2.0.0000.00 and less than 2.0.3002.23,
OLE DB is compliant if the version is
greater than or equal to 1.50.9801 and less than 2.0.0000.00, or
greater than or equal to 2.0.3002.23, or
greater than or equal to 2.10.0000.00
| |
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.
|
