Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
FoxPro Y2K issue
Message
De
10/11/1999 12:14:18
 
 
À
10/11/1999 12:09:32
Information générale
Forum:
Visual FoxPro
Catégorie:
FoxPro 2.x
Divers
Thread ID:
00289646
Message ID:
00289658
Vues:
21
>>>Hi,
>>>Is there any problem when I convert all my "get" date variable fields into character fields and then convert it to date. The reason for this is to make sure that the user enters the four digit year. Thanks.
>>>
>>
>>There are known issues with the FP CTOD() function. I'd suggest investing in a canned solution like Y2KFOX, or simply turning on SET CENTURY ON throughout your system - you are at no more risk of error with that than with date conversion.
>
>What I plan to do is to have a general VALID function on all of my get (date fields) statement. Here are the conditions on the valid:
> IF LEN(ALLTRIM(tcDate1)) < 10 .OR. ;
> CTOD(tcDate1) == {} .OR. ;
> VAL(RIGHT(tcDate1,4)) < 1900 THEN return .f.
>
>Thanks Ed for replying

I remember a problem with 02/29/2000 internal to FP. I've converted the last of my in-house apps to VFP, and was very pleased with Y2KFOX, which bought me the time to do it right rather than try to kludge along with legacy code.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform