Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Is there Y2K problem in FoxPro ?
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00056026
Message ID:
00056475
Views:
39
<snip>
>Actually the problem is coming because SYS(10) function is displaying date field . Sys(11) function is displaying 01/03/0000 means
>1st century B.C. March 1st.
>
>and other date functions are working properly in the range Foxpro Help specified only
>
>By the way, 2000 is leap year, 1600 is leap year. 0400 is leap year. and so B.C. is also a leap year. May be because of that Sys(11) function is giving upto March 1st 1st B.C.
>
>Is really 1st B.C. is leap year?

The reason the calendar was changed in 1752 was because the old calendar had drifted ahead because the old leap year occurred every 4 years even if it was a century year. The reformed calendar specified that a century year was only a leap year if divisible by 400 to keep the calendar in sync. This means that 1700, 1600, 1500, 1400, ... are all leap years
Steve Ruhl
CitiMortgage, Inc.
steven.ruhl@citibank.com Office
Steve@steven-ruhl.com Home
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform