| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Visual Database Tools 6.0 (Russian) - 32-Bit Win
| Product Summary |
Product: Visual Database Tools
Version: 6.0 |
Category: Compliant*#
Operating System: 32-Bit Win |
| Language: Russian |
Release Date: 01 Jul 1998 |
| Operational Range: |
- |
| Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes |
| Prerequisites: |
Windows NT 4 with Service Pack 3 or higher, Windows 9x, MDAC 2.0-Service Pack 2, 2.1, or higher, Visual Studio 6 Service Pack 3. |
| Product Dependencies: |
Visual Basic 6.0 Enterprise, Visual C++ 6.0 Enterprise, Visual InterDev 6.0, Windows NT 4 Service Pack 3 or higher, Windows 9x, OLEAUT32.DLL. |
| Clock Dependencies: |
System Clock, OLEAUT32.DLL |
| Last Updated: |
24 Aug 1999 | |
| Product Details |
|
Visual Database Tools
- Query Designer
- Database Designer
- Table Designer
Czech, Hungarian, Polish, Portuguese (Brazil), Romanian, and Russian contain U.S. software.
Operational Range for Data:
SQL Server 6.5, 7.0: 1/1/1753 AD to 12/31/9999 AD
Oracle 7.3: 1/1/4712 BC to 1/1/4712 AD
Access: 1/1/100 AD to 1/1/9999 AD
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement?
Yes (See Oracle Issues below.)
How the product runtime handles dates:
The database tools do not have a runtime environment.
Two-digit shortcut handling:
Dates are only used in two places in the database tools, both are in the Query Designer:
The Results Pane allows the user to add new rows of data to their backend database table. Values entered into a date-type grid cell are handled by OLEAUT32 and displayed according to the "Short Date" format in the Calendar section of the Regional Settings Control Panel. A 2-digit year is thus interpreted using the same OLEAUT32 Regional Setting for 2-digit year interpretation, which is between the years 1930 and 2029 by default. Entering a 4-digit value within this range will display it as 2-digits, and a 4-digit value outside this range will be displayed as 4-digits.
The Grid Pane allows the user to specify date selection criteria. Here a date value can be entered into the "Criteria" cell, which will be parsed upon exiting the cell. Using a non-SQL Server/Oracle ODBC connection, date values are converted to an explicit 4-digit format. The interpretation of 2-digit years is once again handled via the OLEAUT32 Regional Settings for 2-digit year conversion.
However, when using a SQL Server connection, valid date values entered into the Grid PaneÆs "Criteria" cell are not interpreted via OLEAUT32 settings. They are placed into the SQL pane unchanged. There, SQL Server will interpret a 2-digit year as the century "1900" for values greater than or equal to 50, and as "2000" for values less than 50.
These are design-time issues only; the database tools do not operate in a runtime mode.
Oracle Issues
There is an issue regarding 2-digit year parsing when connecting to an Oracle database with a system configured for 2-digit year format. If the year entered into the Grid PaneÆs Criteria cell is between 2029 and 2000 (the system default 2-digit year window for year 2000 dates) 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 between 1929 and 1900.
The work-around for this is to set your systemÆs Short Date format to include a 4-digit year.
However, this issue is resolved by installing Visual Studio 6 Service Pack 3.
Recommended practices to develop year 2000 compliant applications:
It is highly recommended that the user switch the Short Date format for year in Regional Settings Control Panel to one with 4-digits, (i.e. "M/d/yyyy") to reduce confusion when working with 2-digit years.
Additionally, it is good practice to use a 4-digit year whenever working with dates.
When working against a SQL Server database, it is advisable to set your Regional Settings Control Panel 2-digit year interpretation to mirror that of your server. By default, this is "1950" and "2049" respectively.
Common development errors dealing with year 2000 date issues:
When working against a SQL Server database on a system with the default 2-digit year in the Short Date format and "1930 to 2029" 2-digit year interpretation, a user could enter a date value into the Results Pane between the years 30 and 49. (This will be stored as the year 1930 to 1949 on the backend.) Upon performing a SELECT statement, such as "SELECT * FROM <table> WHERE <datecolumn> > æ1/1/35Æ", only the year 2035 records and higher will be displayed. In this case, it is best to follow the recommended practices mentioned above.
Testing guidelines and recommendations:
Version 6.0 of the Query Designer utilizes ADO, OLEDB, and ODBC functionality to administer user-edits in the Results Pane. Since the Query Designer is designed to work with any ODBC data source, including non-Microsoft drivers, it is advised that customers first test 4-digit date entry on sample databases to verify that dates are handled appropriately. While Microsoft has ensured that their databases and connection mechanisms are year 2000 compliant, it is possible to use the Query Designer with non-Microsoft databases and connection mechanisms. | |
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.
|
