Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP 6.0 Update...(no pun intended)
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00124774
Message ID:
00124856
Views:
21
>>Hi George ---
>>
>>>In a another thread, I mentioned that LUPDATE() wasn't Y2K compliant. After checking the Release Candidate of VFP 6.0, I'm pleased to let you know that in 6.0 it is.
>>>
>>>After setting my system clock to the year 2000, I modified a table in VFP 5.0. The value returned by ? YEAR(LUPDATE()) was 1900. However, in opening the same table (after having set my system clock back to 1998, ? YEAR(LUPDATE()) returned 2000.
>>
>>Hmmm....If the system clock is set to 2000 and you modify a table, LUPDATE() returns 1900? That's weird and a bit worrysome. What were your SET CENTURY ... ROLLOVER settings, if any?
>
>Hi again,
>
>ROLLOVER is 50 years previous by default.


Here's another note to make. In all current and previous version of Fox, SET CENTURY OFF was the default. In VFP 6.0, SET CENTURY ON is the default.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform