Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Ambiguous date
Message
De
12/02/2000 22:48:35
 
 
À
12/02/2000 22:35:54
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Titre:
Divers
Thread ID:
00331435
Message ID:
00331456
Vues:
16
>Thanks for the reply. You have hit on a subtle but important difference. With strictdate set to 1, when I assign a value to the memory variable with the name of the view parameter, (i.e., vp_dDate = {^2000-01-31}), in the command window, the browse for the view works fine. If you release the variable and put the same value in the view parameter dialogue box, you get the "Ambiguous date/datetime constant" error. There seems to be a problem with the dialogue box. I have tried this with several simple views on a test basis and get the same result every time. I am wondering if it is only me or is it with Foxpro. (using Ver 6.0 SP3).


It strikes me that perhaps you're complicating things by using the strict datewrapper here. The dialog knows that it's accepting a data. If it's accepting a string, I don't have to wrap it in quotes. What happens if you just enter a non-ambiguous date in whatever the current system form is, less the strict date notation? I just tried a test, and entering the date in the form {^2000-02-12} gave me the error, but 2000-02-12 did not.
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