Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
More problems with the OleDb provider
Message
De
29/09/2006 00:35:15
 
 
À
28/09/2006 16:26:30
Information générale
Forum:
ASP.NET
Catégorie:
Bases de données
Versions des environnements
Environment:
VB 8.0
OS:
Windows XP SP2
Database:
Visual FoxPro
Divers
Thread ID:
01156780
Message ID:
01158046
Vues:
32
>>"Name" is a reserved word in VFP. It seems the last couple of times you've had reliability problems you've been using reserved words in some fashion. Can you try another way?
>
>This think about reserved words could be an issue. On the last 10 errors, I was able to put the SQL in here, the VFP forum, and the parser was showing in blue color some of the reserved words associated with either the field names, the AS clauses or the aliases. Just to be sure if that could be an issue, I was able to locate one of those SQL commands where only the AS clause was in effect. So, I adjusted the AS clause for a word not reserved. As that was the only place in that SQL command containing a reserved word, we will see how it goes. If this one never comes back, within about 24 hours, I will adjust the others. When it is only the AS clause, it is not a big problem. The big problem is on all those places where I would have to change the table name and the field name. This is in regards to martial arts. So, we have tables named Style.dbf and Master.dbf. And, of course, to my big surprise, even Style is reserved.

It will be interesting to see, let us know your findings.
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