Microsoft KB Archive/209733

= WD2000: WordBasic.Date$, Day$, Month$ Return Incorrect Leap Year Value =

Article ID: 209733

Article Last Modified on 6/17/2005

-

APPLIES TO


 * Microsoft Word 2000 Standard Edition

-



This article was previously published under Q209733



SYMPTOMS
When you use the following WordBasic commands in Visual Basic for Applications,

WordBasic.Date$

WordBasic.Day$

WordBasic.Month$

the commands return March 1 for the Date$, 1 for Day$, and 3 for Month$ when the argument is a serial number corresponding to the last day of February in any year that is equal to or greater than the year 2100 and that is evenly divisible by 4 (leap years).

The following macro demonstrates this behavior.

NOTE: To run this example, first set your date format in your Windows regional settings to mm-dd-yyyy (or any other format that displays all four digits of the year).

Sub LeapYearExample Debug.Print WordBasic.Date$(73108) Debug.Print WordBasic.Date$(73109) Debug.Print WordBasic.Date$(73110) Debug.Print WordBasic.Date$(73111) End Sub

Running the macro produces the following result:

02-27-2100

03-01-2100

03-01-2100

03-02-2100

where the following results would be expected:

02-27-2100

02-28-2100

03-01-2100

03-02-2100



RESOLUTION
To resolve this problem, use the Visual Basic DateSerial function to perform date calculations.

For more information about DateSerial, in the Visual Basic Editor, click Microsoft Visual Basic Help on the Help menu, type DateSerial Function in the Office Assistant or the Answer Wizard, and then click Search to view the topic.



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



MORE INFORMATION
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

Additional query words: vba y2k

Keywords: kbbug kbnofix KB209733

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.