| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Outlook 98 (Czech) - 32-Bit Win
| Product Summary |
Product: Outlook
Version: 98 |
Category: Compliant*
Operating System: 32-Bit Win |
| Language: Czech |
Release Date: 01 Mar 1998 |
| Operational Range: |
01 Apr 1601 - 31 Aug 4500 |
| Prerequisites: |
cc:Mail (ccmailsp.exe) and O98dtfix.exe for the Outlook 98 Import and Export update |
| Product Dependencies: |
Windows 9x or Windows NT 4.0 (Windows NT 4.0 users must install Service Pack 3 for Windows NT 4.0 before installing Outlook 98.) |
| Clock Dependencies: |
Operating System Clock |
| Last Updated: |
15 Jun 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 98 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.
Prerequisites: The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 98 ValuPack is Year 2000 compliant only with the update referenced in the following Microsoft Knowledge Base article Q190629
Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 098dtfix update please see Knowledge Base article Q193604.
Description of how the product handles dates:
Storage. All dates in Outlook 98 are stored and manipulated as full, 4-digit. Dates are integral to the product's operation. In all instances the system clock is used for current date and time data.
Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet.
Parsing on date entry. Outlook 98 employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date.
2-digit shortcut handling:
For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated.
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, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079.
Importing 2-digit year information from text files into Outlook may result in some years being interpreted incorrectly. For additional information on this issue, please refer to the Microsoft Knowledge Base article Q193604
Common date usage errors:
|
1. |
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 will not be correct. |
|
2. |
For full compliance when using Outlook 98 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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 |
|
3. |
The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 98 ValuPack is Year 2000 compliant only with the update referenced in the following Microsoft Knowledge Base article Q190629 |
Testing guidelines and recommendations:
In general, avoid testing in a production environment because we cannot predict side effects with other non-compliant products. 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 may be set off during this testing and will not re-notify when date is set back.
Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired 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 and Long date fields on custom EFD 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 details on Visual Basic 4.0 compliance issues.
See the Microsoft Exchange Server Product Guide for details on server compliance issues.
See the Microsoft Internet Explorer Product Guide for details on Internet Explorer compliance 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.
|
