Microsoft KB Archive/265012

From BetaArchive Wiki
Knowledge Base


OL2000: Some Date Formats Cause Error with Specific Dates in Japanese Version of Outlook 2000

Article ID: 265012

Article Last Modified on 10/6/2005



APPLIES TO

  • Microsoft Outlook 2000 Standard Edition



This article was previously published under Q265012

SYMPTOMS

When you use some date formats to find or restrict items in Outlook in a Japanese locale, you may receive the following error message with specific dates such as September 29, 2000. This problem can occur within a 256-day period from January 7, 2000.

Run-time Error '-2147352567 (80020009)': Type mismatch or the value "xx/xx/xx xx:xx" in the condition is not valid.

The date format that causes the problem may vary as follows:

Date Format Operating System
yy/mm/dd HH:MM Microsoft Windows NT 4.0
yyyy/mm/dd (ddd) HH:MM Microsoft Windows 2000


CAUSE

This problem is caused by Outlook. In Outlook, the work space (stack) of the data format string is also used for acquisition of the current time, and it is reused without initialization.

If the Restrict method is used on January 17, 2000, the current time in internal form that is preserved in the work space is recognized as a part of data format string when the work space is used again. As the result, the date specified with the Restrict method can't be recognized properly, and an error occurs.

The same phenomenon occurs for 256 days in the period, like on June 12, 2001 and on September 29, 2000.

NOTE: This phenomenon depends on the client's current time, and doesn't depend on the date specified with the Restrict method.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Office 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

276367 OFF2000: How to Obtain the Latest Office 2000 Service Pack


WORKAROUND

To work around this problem, use the "yyyy/mm/dd HH:MM" date format in the Restrict method.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbbug kbfix kbqfe kboffice2000presr2fix KB265012