Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
DATE() error
Message
From
18/09/2008 23:12:51
Neil Mc Donald
Cencom Systems P/L
The Sun, Australia
 
 
To
18/09/2008 12:17:48
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Title:
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Vista
Network:
Windows 2003 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01348495
Message ID:
01348814
Views:
12
Hi,
Ignore the original post, the error is not in VFP but Java, we do a function call to a Java library and it has the problem.

Does Java run it's own clock, which is drifting?

>>Hi,
>>Is anyone having problems with the DATE() function returning dates in the future ?
>
>It is well known that all version of Fox, starting with FoxPlus in 1988 and on, have the Y10K bug - dbfs are incapable of storing dates beyond year 9999; datetimes could store that but VFP can't show those dates and reports them as blank:
>
>x=DATE(9999,12,31)
>?x
>x = x + 1
>?x
>but
>?x-34
>still returns a valid date, which means a variable can hold a date after 31-dec-9999 but it can't be displayed directly - you would have to roll your own.
>
>CREATE CURSOR uu (t t)
>x=DATEtime(9999,12,31, 23,22)
>INSERT INTO uu VALUES (x)
>INSERT INTO uu VALUES (x+2300)
>BROWSE
>go bott
>?t-33
>
>Last line displays a blank, which means VFP actually refuses to store such variables into datetime fields.
>
>That's a bug, and I don't expect it will be fixed, ever. If it does, it will be at the last minute, not our problem.
Regards N Mc Donald
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform