| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Visual Studio 6.0 (German) - 32-Bit Win
| Product Summary |
Product: Visual Studio
Version: 6.0 |
Category: Compliant*#
Operating System: 32-Bit Win |
| Language: German |
Release Date: 01 Aug 1998 |
| 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 95, Windows 98, Windows NT 4.0 Service Pack 4 plus Year 2000 software updates, Internet Explorer 4.01 Service Pack 1 |
| Clock Dependencies: |
System Clock, Operating System File Date API, OLEAUT32.DLL. |
| Last Updated: |
20 Aug 1999 | |
| Product Details |
|
This report applies to:
Enterprise and Professional editions.
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes
NOTE:
One or more of the bundled products or components in Visual Studio 6.0 has known issues. These products are listed below under section II of "Product Details." Please refer to this section for more information.
Operational Range for Data: See individual product detail for products listed below.
Outlook Express 4.01 date handling:
If Outlook Express (OE) 4.01 (Service Pack 1 or Service Pack 2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), than the year will be interpreted as the current year plus 98 (e.g. 2098). You can find more information about this fix in the Internet Explorer (32-bit) 4.0x Year 2000 disclosure document at http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430.
Prerequisites:
A prerequisite refers to what is needed for a given product to reach the compliance classification indicated. It could include a software update that is required or a specific version of a related Microsoft technology that the product needs.
Product Details
There are three aspects of Year 2000 compliance for Visual Studio 6.0: compliance for the individual visual tools in the suite (such as Visual Basic and Visual C++), compliance of other Microsoft Products which ship as a part of Visual Studio (such as SQL Server Developer Edition), and compliance of the suite-specific features such as Visual Studio Analyzer, Installer tools, and Visual Component Manager.
- Visual Studio 6.0 tools
The Year 2000 status of the Visual Studio 6.0 individual tools is described below. Please refer to the individual tools and their prerequisites in the Microsoft Year 2000 website for information on compliance status as well as specific information on date handling, recommended practices, usage errors, and testing guidelines:
|
Visual Studio 6.0 development tool |
Design Time Compliance |
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? |
Product Dependencies |
|
Microsoft« Visual Basic« 6.0 |
Compliant*# |
Yes
(with recommended updates applied) |
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT4 with Service Pack 4 û Year 2000 software updates recommended |
|
Microsoft« Visual C++« 6.0 |
Compliant* |
Yes
(with recommended updates applied) |
Windows 95, or Windows 98, or Windows NT 4.0 with Service Pack 4 - plus Year 2000 software updates |
|
Microsoft« Visual FoxPro« 6.0 |
Compliant |
Yes
(with recommended updates applied) |
Windows 95, Windows NT4.0 Service Pack 4- plus Year 2000 software updates, Windows 98, Windows 2000 |
|
Microsoft« Visual J++Ö 6.0 |
Compliant |
Yes
(with recommended updates applied) |
Windows 9x, Windows NT 4.0 with Service Pack 3 - plus Year 2000 software updates |
|
Microsoft« Visual InterDevÖ 6.0 |
Compliant* |
Yes
(with recommended updates applied) |
Internet Explorer 4.01 Service Pack 1, Internet Information Server 4, Front Page 98, ODBC 3x, MDAC 2.0, Scripting4 |
|
Microsoft« Visual SourceSafeÖ 6.0 |
Compliant |
Yes
(with recommended updates applied) |
None |
- Additional Microsoft Products within Visual Studio 6.0
Visual Studio Enterprise Edition also contains these additional Microsoft Products.
|
Additional Products in Visual Studio 6.0 |
Known
Issues |
Recommended Action |
|
Microsoft Windows NT4 Service Pack 3 |
Yes |
Download Windows NT4 Service Pack 4 - plus Year 2000 software updates to be compliant:
Windows NT Service Packs |
|
Microsoft Internet Explorer, version 4.01 |
Yes |
A product update is available at Internet Explorer 4.01 update.
|
|
Microsoft SQL Server Developer Edition, version 6.5 |
Yes |
SQL Server 6.5 requires service pack 5 to be compliant: |
|
Microsoft Windows NT Options Pack |
Yes |
Requires Windows NT Service Pack 4 plus Year 2000 software updates, or later service pack- for compliance:
Windows NT Service Packs |
|
Microsoft FrontPage 98 (single user) |
No |
none |
|
SNA Server 4.0 (with Service Pack 1) |
No |
none |
|
Microsoft Transaction Server Developer Edition, version 2.0 |
No |
none |
|
Microsoft Visual Database Tools |
Yes |
Download Visual Studio Service Pack 3 |
Visual Studio 6.0 Enterprise Edition also includes the following third party add on components which are not included in the above test results:
- Install Shield, version 5.0
- Suite Specific Features of Visual Studio 6.0
Visual Studio Enterprise Edition 6.0 also contains several suite specific features. Please refer to the below for specific information on date handling, recommended practices, and testing guidelines.
How the product runtime handles dates:
The Visual Studio Analyzer tool and the Application Performance Explorer convert dates to a 4-digit format, sorts them, truncates them to 2 digits, and then displays the results.
The Visual Component Manager tool passes the date inputs as a string type to the database (SQL or Access). Therefore, the Year 2000 status of the database being used needs to be determined.
The Installer tools compare file timestamps by comparing the time_t data type. Dates for each of these Enterprise Edition Components are stored in a time_t data type format.
Two-digit shortcut handling:
Visual Studio Analyzer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field.
Application Performance Explorer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field.
Visual Component Manager component: Two-digit shortcuts are supported, but the date field is passed to the database for query. Therefore, this toolÆs ability to interpret dates in the correct century is affected by the database used.
Two-digit dates in the Microsoft Application Performance Explorer 6.0, Microsoft Visual Studio Analyzer 6.0, and Microsoft Visual Component Manager 6.0 tools pass the string to the database for querying. Therefore, the toolÆs ability to interpret dates correctly is affected by the database used.
Recommended practices to develop year 2000 compliant applications:
- Microsoft Windows NT 4.0 requires Service Pack 4 plus Year 2000 software updates.
- Install Microsoft SQL Server 6.5 Service Pack 5. More details are available in the SQL Server Compliance document available on this web site.
- Install the latest version of the Microsoft comctl32.dll or update comctl32.dll to the latest version from http://www.microsoft.com/msdownload/ieplatform/ie/comctrl.asp to update the Internet Explorer 4.0 Date/Time Picker and Month Calendar control leap day issue.
- Install the update for the Microsoft Data Access Components, which will be shipped as part of Windows NT 4.0 Service Pack 4.
- Install the updated Microsoft Virtual Machine, version 2436 or 3165 or later, from http://www.microsoft.com/java/download.htm.
Visual Studio Database Tools: Oracle and Visual Studio Query Designer may interpret 2-digit year dates differently
When using the Visual Studio 6.0 Query Designer against an Oracle database, it is highly recommended you set your regional settings to a 4-digit year setting such as MM/DD/YYYY to prevent incorrect or unexpected results from queries that could lead to data loss. When a date is entered into the Grid Pane of the Query Designer, it is formatted according to the regional settings. Then, this reformatted date is passed to Oracle, which interprets the date string according to the serverÆs configuration. If the year entered into the Grid PaneÆs criteria cell is from 2000 through 2029 (the system default 2-digit year window for dates 2000 and later), the date will be converted by OLEAUT32 into a 2-digit value when parsed into the SQL Pane. Oracle will interpret this as a year from 1900 through 1929.
For example: A user types the date "1/1/2001" into the Grid PaneÆs criteria cell. With two digit years turned on, the date is reformatted to "1/1/01." When Oracle receives the string it interprets the date "1/1/01" to be "1/1/1901." If the date is being used in the criteria for an UPDATE or DELETE query, data loss may occur.
This issue is addressed in the final release of Visual Studio 6.0 Service Pack 3.
Testing guidelines and recommendations:
Set the system clock on a non-production system to a time like 11:50 pm Dec 31, 1999 and let it automatically roll to the year 2000 and see if the application still works as expected.
| |
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.
|
