>>Hi Missy,
>>
>>I haven't been on the Thread in a while - you probably have found the answer by now to your question! Anyway, as far as I know Leap Year 2000 should not be a problem in FoxPro 2.6 - it's not in our app. FoxPro uses 4 digit date fields, and I've researched the fact that Leap year 2000 is not a problem either.
>
>The problems is not in supporting the date... the problem is in entering it in the UI...
>
>Go into one of your 2.6 aps and find a date field, try to enter the following, legitamate, Y2K date...
>
>2/29/00
>
>... of course, it doesn't let you... unless you put in...
>
>2/29/2000
>
>That is the issue.
>
>BOb
That's because "normal" century years are not leap years -- otherwise we'd get ahead of ourselves. Presumably a millenium year is a leap year (I wasn't around for the last one so I don't remember if it was or not)

I think we should just pick up the planet and move it slightly so that its orbit corresponds to an exact (& non-prime) number of days. Then we could have a calendar that made sense.

Jen