| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Visual Basic (32-bit) 5.0 (German) - 32-Bit Win
| Product Summary |
Product: Visual Basic (32-bit)
Version: 5.0 |
Category: Compliant*#
Operating System: 32-Bit Win |
| Language: German |
Release Date: 01 Jan 1997 |
| Operational Range: |
- |
| Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes |
| Prerequisites: |
See Below |
| Product Dependencies: |
Windows NT 4.0 Service Pack 4, Windows 95 (+ year 2000 software updates), Windows 98 (+ year 2000 software updates), Windows 98 (plus Y2K updates), Year 2000 update for Internet Explorer 3.02, SQL Server 6.5 Service Pack 5, MDAC 2.0 Service Pack 2 |
| Clock Dependencies: |
System Clock, Visual Basic runtime, (OLE) Automation Libraries |
| Last Updated: |
28 Sep 1999 | |
| Product Details |
|
This report applies to:
VB 5.0- Learning, Professional, Enterprise
Czech, Polish, Portuguese (Brazil), and Russian contain US Software.
Developing Year 2000 Compliant Software
Operational Range for Data: 1930 through 2029 using two-digit shortcuts or user configurable
How the product runtime handles dates:
While all versions of Visual Basic will handle years greater than 1999 (in a 4-digit format), passing a 2-digit year in a date (such as 7/3/45) requires Visual Basic to interpret to what century the date corresponds.
Two-digit shortcut handling:
Visual Basic 5.0 converts 2-digit years to 4-digit years based on the default in the Automation libraries for all date functions. Visual Basic 5.0 shipped with version 2.20.4054 that converts 2-digit years to the 2000s if the 2-digit year is between 00 and 29. If the 2-digit year is between 30 and 99, the date is converted to the 1900s. The product will function into the 21st century through the end of year 2030 in accordance with industry standard 100-year date windowing. Developers can modify this date window to their own needs as described in the Windows 98 control panel or as described in the white paper, "Developing Y2K Compliant Applications with Visual Basic"
Recommended practices to develop year 2000 compliant applications with this Development Tool:
Users can use their own set of rules instead of relying on the defaults native to Visual Basic. For example, users may enter only a 2-digit year and have 00 to 49 correspond to the years 2000 to 2049 and have 50 to 99 correspond to the years 1950 to 1999.
When accepting a date string from the user, test the format of the string to determine the number of digits entered for the year. According to the rules for this sample application, 1/11/45 is in the year 2045, and not in the year 1945. Within the code for the application, change the string to use the appropriate 4-digit year, and then convert that date string with the 4-digit year into a date variable.
Please refer to the white paper, "Developing Y2K Compliant Applications with Visual Basic"
Common development errors dealing with year 2000 date issues:
Please refer to the white paper, "Developing Y2K Compliant Applications with Visual Basic"
Other design time issues to be aware of:
If the products or technologies listed below are installed, they should be updated to ensure proper functioning:
Note for Enterprise Edition Users
Visual SourceSafe contains a small cosmetic display issue when using the history pre-dialog:
1. In the History pre-dialog where users can specify a date range to do a history on ("show me the History between 1/1/97 and 2/24/2000), if users specify a date after the year 2000, it will be treated as a date in the 1900s. The same problem exists on the command line.
2. The history pre-dialog in version 5.0 does not accept 4-digit years.
The issues described above are cosmetic display problems. Data is stored correctly and clock rollover to the year 2000 will not cause data loss.
The most restrictive structure Visual SourceSafe uses for dates is a long integer containing the number of seconds since January 1, 1970.
Testing guidelines and recommendations:
Please refer to the white paper, "Developing Y2K Compliant Applications with Visual Basic"
| |
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.
|
