The information in this article applies to:
SYMPTOMSIf you use a Date field in a form that was created with Exchange Forms Designer (EFD), which is a stand-alone 16-bit Visual Basic run-time utility, the dates do not work as expected for dates with year values 2000 or greater. For example, if you type the date 01/28/00 into the Date field, the displayed result is Sunday, January 28, 1900, instead of Friday, January 28, 2000. CAUSE
Exchange Forms Designer is not year 2000 (Y2K) compliant. EFD changes the two-digit date value to 19XX, where XX is the date value entered.
http://www.microsoft.com/technet/year2k/product/user_view71810EN.htm RESOLUTIONThere is no resolution for this issue. Outlook 97, Outlook 98, and Outlook 2000 have their own 32-bit Forms Design routines that are Y2K compliant, and correctly display a date in the form 01/28/00. WORKAROUNDUse Outlook 97, Outlook 98, Outlook 2000, or 32-bit Visual Basic to design your forms. MORE INFORMATIONSteps to Reproduce ProblemThe following steps are for Outlook 98, but you can reproduce the problem in Outlook 97 and Outlook 2000 as well.
The date changes to Sunday, January 28, 1900. Expected Result: The date should change to Friday, January 28, 2000. NOTE: If you type the date with four digits for the year (for example, 01/28/2000), then it correctly displays the expected date. Similarly, if your system date is changed so that the current year is 2000-2099, then "00-99" are converted to 2000-2099. Additional query words: OL98 OL97 OL2000
Keywords : kbdta |
Last Reviewed: November 27, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |