| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Outlook (Win 3.1) 8.XX (Japanese) - 16-Bit Win
| Product Summary |
Product: Outlook (Win 3.1)
Version: 8.XX |
Category: Compliant#
Operating System: 16-Bit Win |
| Language: Japanese |
Release Date: 01 Oct 1997 |
| Operational Range: |
01 Jan 1980 - 31 Dec 2035 |
| Prerequisites: |
None |
| Product Dependencies: |
Windows 3.1; Exchange Server 4.0 Service Pack5 or Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 2 or greater. |
| Clock Dependencies: |
Operating System Clock |
| Last Updated: |
08 Jan 1999 | |
| Product Details |
|
How the product handles dates:
- Storage. Dates in the Outlook for Windows 3.1 client are stored and manipulated as full 4-digit dates. Both the serverÆs and clientÆs system clocks are used for current date and time data. Date storage and manipulation uses a 32-bit long word that supports date/times throughout the operational range of January 1, 1970 û January 31, 2039. See Common date usage error below.
- Formatting. Dates are displayed with and 2-digit or 4-digit year formats, using the short date format (YY) and long date format (YYYY) specified in the Date & Time applet in the Control Panel. The date entry fields in the Find/Filter Items dialogue accept only inputs in 2-digit or 4-digit year format. See Date Entry Parsing below.
- Date Entry Parsing (messaging features). The only date entry fields in the messaging features of the client are those in the Advanced Find and Filter Items dialogs, which are also used by the Inbox Assistant and Out Of Office Assistant. These fields accept only 2-digit year inputs. Inputs in the range of 80 - 99, 00 - 35 are parsed into years 1980 through 2035, regardless of what the current year is.
- Date Entry Parsing (calendaring features) Date entry dialogs accept in 2-digit or 4-digit year formats, using the short and long date formats specified in the Date & Time applet in the Control Panel. Inputs in 2-digit year format in the range of 80 û 99, 00 û 35 are parsed into years 1980 through 2035, regardless of what the current year is. Inputs in 4-digit year format in the range 1900 û 2035 are parsed as entered. Issue: Inputs in 4-digit year format in the range 0100 û 1899 are parsed as 1900. Inputs in 4-digit year format in the range 0000 û 0099 are parsed as 1900 û 1999 respectively. Workaround: When editing a contact's birthday or anniversary date, use the dropdown calendar to select a date or enter the year as four digits (example: 2001).
Two-digit shortcut handling:
Two-digit year entries in the range of 80 û 99, 00 û 35 in the Exchange Client are parsed into years 1980 through 2035. Two-digit displays use the short date format specified in the Date & Time applet in the Control Panel.
Common date usage error:
For end-to-end compliance when using the Outlook for Windows 3.1 client, users need a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 2 or greater.
Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc.
Testing guidelines and recommendations:
In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely.
See Exchange Server compliance information for details on server issues.
| |
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.
|
