Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Weird MySQL Behavior
Message
De
15/02/2011 04:55:31
 
 
À
15/02/2011 04:48:38
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 SP2
OS:
Windows 7
Network:
Windows 2003 Server
Database:
MySQL
Application:
Desktop
Divers
Thread ID:
01500180
Message ID:
01500183
Vues:
67
Just a wild guess; have you tried pohdr.terms instead of a.terms? If you already have an open table or cursor, it will may the alias of A, so the CA may guess that you refer to the open table/cursor. This is why I avoid using A-J and M as aliases.

>Viv,
>
>I tried this one (using a different Where clause):
>
>SELECT A.REFNO, A.DATE, A.SUPPLIERID, A.TERMS, A.TOTQTY, A.AMOUNT, A.REMARKS,
>     A.PREPAREDBY, A.CHECKEDBY, A.PRINTDATE, A.POSTDATE, A.CLOSED, A.CANCELLED, A.ID,
>     B.CODE AS SUPPCODE, B.DESCRIPTOR AS SUPPNAME, B.ADDRESS AS SUPPADDR
>FROM pohdr A JOIN SUPPLIER B ON A.SUPPLIERID=B.ID  WHERE A.TERMS=30
>ORDER BY REFNO
>
>
>Got the same "Unknown column... in 'where clause'" error.
>
>Am getting really really frustrated.
>
>Dennis
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform