Microsoft TechNet - Year 2000



This static CD-based web site is representative of the www.microsoft.com/y2k site as of October 15, 1999.

Microsoft Year 2000 Readiness Disclosure & Resource Center

ODBC Core Components 2.5 (English) - 32-Bit Win

Product Summary

Product: ODBC Core Components
Version: 2.5 Category: Compliant*#
Operating System: 32-Bit Win

Language: English Release Date: N/A

Operational Range: -

Prerequisites: Compliant versions of Windows NT 3.51 or Windows 95, msvcrt.dll, mfc40.dll

Product Dependencies: None

Clock Dependencies: datetime data will correspond to the data source. ODBC drivers use the system clock to supply the date when converting from time (no date specified) to date-time.

Last Updated: 03 Apr 1999

Product Details

Operational Range for Data: Dependent on Data Source

Release Date: 1995

Product: Microsoft ODBC core components (Driver manager, Cursor library, ODBC Administrator)

ODBC is a Data Access application programming interface (API) that exposes data from a variety of Data Sources.

How the product handles dates:

ODBC standard date syntax and escape formats disallow the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure.

Two-digit shortcut handling:

The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server.

Common date usage errors:

ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent.

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date interpretation features of most backend data stores, Microsoft recommends using 4-digit year formats in dates, particularly when placing data into a store and querying that store.

Platforms applicable:

x86 and Alpha machines.

Power PC and MIPS were not tested, as support for these platforms has been discontinued.

Known Issues:

In ODBC 2.x , there are two installer APIs with year 2000 issues. The APIs in question are: SQLInstallDriver and SQLInstallODBC. These APIs were used to write custom setups for ODBC drivers.

SQLInstallODBC was discontinued after ODBC 2.5.

SQLInstallDriver still exists in later versions of ODBC, but the option to use an INF (the source of the problem), was removed in ODBC 3.0. In addition, ODBC 3.0 added a new preferred API, SQLInstallDriverEx.

Under what circumstances would the problem occur?

If someone wrote a setup using SQLInstallDriver or SQLInstallODBC from ODBC 2.5,

AND they used an INF,

THEN during install, the date evaluation may not be done properly, resulting in wrong files version being installed, or files being installed with incorrect filedates.

The installer APIs are in odbccp32.dll for 32bit apps, and in odbcinst.dll for 16bit apps.

Remediation:

The remediation is to use ODBC 3.0 or higher. ODBC 3.x does not support SQLInstallODBC, and does not support SQLInstallDriver with INFs, so the application would get a warning during setup, instead of possibly installing wrong bits.

To determine which version of ODBC is installed, look at the fileversion of odbc32.dll (right click/properties). If it is 2.50.xxxx, it is ODBC 2.5. If it is 3.00.0000 or higher, it is ODBC 3.0 or greater.

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.

This site is being designated as a Year 2000 Readiness Disclosure and the information contained herein is provided pursuant to the terms hereof and the Year 2000 Information and Readiness Disclosure Act.