Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
More problems with the OleDb provider
Message
De
17/09/2006 14:43:07
Al Doman (En ligne)
M3 Enterprises Inc.
North Vancouver, Colombie Britannique, Canada
 
 
À
15/09/2006 10:40:37
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Database:
Visual FoxPro
Divers
Thread ID:
01153726
Message ID:
01154484
Vues:
9
>>"Master" is a reserved word in VFP, maybe in the provider as well.
>
>Do you think this is what could make the OleDb provider go wild on specific occasions only? Usually, when there is something wrong, it should always generate an error. This is what confuses me about this OleDb thing it is that it does it sometimes and some other times not.

Well, you could test by SELECTing everything into a temporary cursor (NOFILTER) with a different alias (e.g. "Master1"), then running your main SELECT against that, to see if that makes a difference.

>
>>For ease of reading and maintenance I'd recommend using local aliases e.g.
>>
>>SELECT A.Numero, ...
>>FROM Master A ;
>>...
>>
>
>Thanks, but IMHO this is one of those things that makes things more difficult to understand. If I see A in front of a field as an alias, basically, it doesn't tell me anything about the original source.

If you want to do the test I outlined above, you make 1 change to the code with local aliases, rather than changing in many places, so maintenance is easier in this case.

As for readability, chacun a son gout, je suppose.
Regards. Al

"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov

Neither a despot, nor a doormat, be

Every app wants to be a database app when it grows up
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform