| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Visual C++ 5.0 (English) - 32-Bit Win
| Product Summary |
Product: Visual C++
Version: 5.0 |
Category: Compliant*#
Operating System: 32-Bit Win |
| Language: English |
Release Date: 01 Feb 1997 |
| Operational Range: |
01 Jan 1980 - 18 Jan 2038 |
| Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes |
| Prerequisites: |
See below |
| Product Dependencies: |
Windows NT 3.51, Windows NT 4.0, Windows 95, Internet Explorer 3.02, Acme Setup, ODBC driver, SQL Server, Microsoft Visual SourceSafe 5.0 (see the Visual Source Safe 5.0 compliance document for more details). |
| Clock Dependencies: |
System Clock |
| Last Updated: |
10 May 1999 | |
| Product Details |
|
This report applies to:
Enterprise, Professional, and Learning editions.
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement?
Yes.
Note: This requires that any available and appropriate software updates or service packs have been applied.
How the product runtime handles dates:
Visual C++ 5.0 uses the following data types for dates:
|
Data type |
Range |
|
time_t |
1/1/1970 through 1/18/2038 |
|
DATE VARIANT |
1/1/100 through 12/31/9999 |
|
struct FILETIME |
The number of 100 nanosecond intervals since 1601 and until the year 58,457,005 A.D. (a 64-bit value) |
|
struct SYSTEMTIME |
The year (since 0 A.D.) in an unsigned 16-bit value |
|
DOS DateTime |
1/1/1980 through 12/31/2108 |
|
SQL_DATE & SQL_TIMESTAMP (ODBC) |
1/1/1970 through 12/31/9999 |
Known Issues:
There is a known date related issue: if the system clock is set to 2000 and the user creates a default Microsoft Foundation Classes (MFC) AppWizard application, the generated program date reads "1900". This does not impact the functionality of the generated program but should be corrected using the resource editor to avoid confusion as to the date the application was created.
Two-digit shortcut handling:
The product provides 2-digit shortcuts for display only.
Recommended practices to develop year 2000 compliant applications:
Please see the "Visual C++ and the Year 2000" best practices article located at http://msdn.microsoft.com/visualc.
Non-Microsoft components:
Oracle ODBC driver
"TimeLock" timebomb component (used in demo versions only)
InstallShield
Product includes non-Visual C++ components with which the user can build applications:
ODBC, OLE DB (Data Access Group)
Month Calendar Control, Access Calendar Control (Office Group)
OLEAUT32.DLL, MS Month View Control, DBGrid, DBCombo, DBList, DataGrid, DataCombo, DataList, FlexGrid, Hierarchical FlexGrid (Visual Basic Group)
Database engines (DAO, Access Jet)
Component Gallery: status bar
Common development errors dealing with year 2000 date issues:
The most likely area for concern arises if users write their own date handling routines. Please see the "Visual C++ and the Year 2000" best practices article located at http://msdn.microsoft.com/visualc
Testing guidelines and recommendations:
Please see the "Visual C++ and the Year 2000" best practices article located at http://msdn.microsoft.com/visualc
| |
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 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.
|
