Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Weird MySQL Behavior
Message
From
15/02/2011 08:27:22
 
 
To
15/02/2011 08:03:07
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 7
Network:
Windows 2003 Server
Database:
MySQL
Application:
Desktop
Miscellaneous
Thread ID:
01500180
Message ID:
01500219
Views:
42
Tore,

what happens if you replace b.descriptor with pohdr.descriptor? Even better, what happens if you replace all As and Bs with for instance AA and BB, in order to avoid single letter aliases? Like this:
SELECT AA.REFNO, AA.DATE, AA.SUPPLIERID, AA.TERMS, AA.TOTQTY, AA.AMOUNT, AA.REMARKS,
     AA.PREPAREDBY, AA.CHECKEDBY, AA.PRINTDATE, AA.POSTDATE, AA.CLOSED, AA.CANCELLED, AA.ID,
     BB.CODE AS SUPPCODE, BB.DESCRIPTOR AS SUPPNAME, BB.ADDRESS AS SUPPADDR
FROM pohdr AA JOIN SUPPLIER BB ON AA.SUPPLIERID=BB.ID  WHERE BB.DESCRIPTOR LIKE 'ABC%'
ORDER BY REFNO


Still the same error sir. =(

Since the exact same statement works in MySQL Query Browser, and works in VFP side, albeit shows an error message first, could it be because something is lost in translation via ODBC?

Dennis
Previous
Reply
Map
View

Click here to load this message in the networking platform