Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Ctod() weirdness
Message
De
11/08/2015 13:12:35
 
 
À
10/08/2015 11:08:36
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows Server 2012
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Web
Divers
Thread ID:
01623085
Message ID:
01623130
Vues:
82
This message has been marked as the solution to the initial question of the thread.
J'aime (1)
>Why would a command such as:
>? ctod("10/13/15")
>give me the following result?
>10/13/2115
>In other words, next century instead of the current century.
>
>I am trying to import data from a text file, and thought ctod() would be a quick solution. Actually the dates seem to include a century, so the question might be irrelevant for this particular task, but I was still curious what I did wrong.
>
>Here are some relevant settings (Visual FoxPro 9):
>set("date") = "AMERICAN"
>set("century") = "ON"
>set("century", 1) = 20
>set("century", 2) = 65
>set("century", 3) = 2029 && what the heck does this do?

Time for an extremely stupid question -- is there any particular reason why you have
SET CENTURY TO 20
instead of
SET CENTURY TO 19
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform