Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
False Reporting of Damaged Index...
Message
De
07/07/1999 10:16:43
 
 
À
06/07/1999 17:12:03
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00237534
Message ID:
00238267
Vues:
12
I ran into something similar, and ended up making my expression ctod(dtoc(mydatefield))

Both version will except that. Or you could just change the strict date setting in VFP until the conversion is done, then fix the indexes and set strictdate back to the default.

>Hi Todd
>
>>I know this is wierd, but its a wierd problem. Try deleting the tags one by one and see if there is one particular index that is creating the problem. Some strange stunt with a udf or something may have been pulled, or maybe a function that has changed it behaviour between the two versions may be in use.
>>
>
>Sorted - figured it out this morning. It is indeed an index problem because the index (carried forward from my dos app) is based on a date expression which the new vfp strictdate analysis finds to be capable of creating "ambiguous dates" and so it throws up an error. Replace the date expression with the new "date(y,m,d)" format and its happy as Larry. The only problem is that I can't do that with the live data as the dos version wont recognise the new date expression, but as there doesn't seem to be any evil consequence, I guess I'll just have to live with it for a few months until I've got all my users converted to the vfp version.
>
>Cheers
>
>Harry
--Todd Sherman
-Wake Up! Smell the Coffee!
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform