| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Outlook 2000 9.0 (Estonian) - 32-Bit Win
| Product Summary |
Product: Outlook 2000
Version: 9.0 |
Category: Compliant
Operating System: 32-Bit Win |
| Language: Estonian |
Release Date: N/A |
| Operational Range: |
01 Apr 1601 - 31 Aug 4500 |
| Prerequisites: |
None |
| Product Dependencies: |
Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later |
| Clock Dependencies: |
System clock |
| Last Updated: |
15 Sep 1999 | |
| Product Details |
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customersÆ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.
How the product handles dates:
- Storage. Dates in Outlook are stored and manipulated as full dates (4-digit year). Dates are integral to the productÆs operation. The system clock is used for current date and time data.
- Formatting. Dates are displayed in 2-digit and 4-digit year formats, using the short date format and long date format specified on the Date tab in Regional Settings in the Windows Control Panel. Default formats include the following format orders: day-month-year, year-month-day, and month-day-year.
- Parsing on date entry. Date entry fields parse and accept inputs that follow the formats specified in Regional Settings. 4-digit year entries are unambiguously parsed and stored as full dates. Please see "Two-digit shortcut handling" below for parsing of 2-digit year entries.
2-digit shortcut handling:
Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings.
On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029.
On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range.
Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office AssistantÆs Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035.
Common date usage errors:
- If you have custom forms that store or display dates, avoid using text fields to store date data. If you store dates in text fields and your script uses this field to calculate another field, the calculation result may not be correct.
- For end-to-end compliance when using Outlook as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or later. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways, and so forth.
- When changing the date formats on the Date tab in Regional Settings from the system defaults, be sure the date orders between the short date and long date formats match, for example, both formats are in day-month-year, both are in month-day-year, or both are in year-month-day order.
Testing guidelines and recommendations:
In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely.
The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back.
Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded.
If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that the Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short date fields and Long date fields on custom Exchange Forms Designer forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) product guide for information about Visual Basic 4.0 compliance issues.
See the Microsoft Exchange Server product guide for information about server compliance issues.
See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.
Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| |
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.
|
