>>I knew FoxPro wouldn't see the century 'cross-over'. I knew that if I was
>>operating in the 1900s and put in a '00' date, FP would see it as 1900.
>>
>>But I ASSUMED (silly me) that when we hit the Y2K, that FoxPro would pick up
>>the cenutry we're in! WRONG!!!!
>
>From the 2.6 documentation:
>
>Use SET CENTURY to specify how date variables and functions are displayed.
>
>ON
> SET CENTURY ON specifies a four-digit year format that includes 10 characters (including date delimiters).
>
>OFF
> SET CENTURY OFF specifies a two-digit year format that includes eight characters and assumes the twentieth century for date calculations. This is the default setting.
>
>
>In later versions, the behavior was changed to match the current century. However, I don't see any real reason to use SET CENTURY OFF in programs -- then there's no way to tell the program that yes, you really did mean 1901 instead of 2001....

Garrett,

This came as a shock to me, but OFF isn't necessarily the default setting in FPW 2.6. If, under Win 9x, the user selects a format for short dates that includes all four digits of the year, FPW (and that ain't a typo) seems to pick up on it. I just saw it a few minutes ago.