Article ID: 202432
Article Last Modified on 2/27/2007
APPLIES TO
- Microsoft Outlook 2000 Standard Edition
- Microsoft Outlook 97 Standard Edition
- Microsoft Outlook 98 Standard Edition
- Microsoft Exchange Server 5.5 Standard Edition
This article was previously published under Q202432
SYMPTOMS
If 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.
For additional information on how Visual Basic 4.0 handles dates, please see the following Microsoft Web site:
RESOLUTION
There 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.
WORKAROUND
Use Outlook 97, Outlook 98, Outlook 2000, or 32-bit Visual Basic to design your forms.
Additional query words: OL98 OL97 OL2000
Keywords: kbnofix kbprb KB202432