Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
CTOD() Totally un-Y2K...
Message
General information
Forum:
Visual FoxPro
Category:
FoxPro 2.x
Miscellaneous
Thread ID:
00311837
Message ID:
00311854
Views:
25
>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....
My blog
My consulting page
My home page

Member of the Trim Your Auto-Quote Campaign!
What's another word for thesaurus?
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform