Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Ctod bug
Message
From
08/06/1998 14:39:16
 
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Miscellaneous
Thread ID:
00105986
Message ID:
00105993
Views:
26
Hiya Derk ---

This is an interesting "feature"....SET DATE TO AMERICAN, BRITISH, GERMAN, ITALIAN, and FRENCH work with dates before 1600....SET DATE TO LONG, SHORT, ANSI, JAPAN, TAIWAN, MDY do not......

I guess a workaround is to SET DATE TO one of the ones that work before doing ancient date calculations.



>
>We found what seems to be a bug, both in VFP 5.0a and VFP6 beta. Maybe some of you have encountered it before, but we never read about it on the Compuserve forum, so we thought we'd post it.
>
>set date to long
>?ctod("01/01/1597") returns nothing (or empty string)
>set date to short
>?ctod("01/01/1597") returns nothing (or empty string)
>set date to YMD
>?ctod("01/01/1597") returns / /
>
>should be 01/01/97, right? Works fine with other date formats. Plus,
>
>set date to short
>?ctod("01/01/1597") + 1500 returns 9-02-01, correct!
>
>We concluded that CTOD doesn't work correct (at least doesn't return correct values) for dates < 01/01/1601. Has anyone seen this before?
>
>greetings,
>derk schutte
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05
Previous
Reply
Map
View

Click here to load this message in the networking platform