| Bug #2530 | MS Query (Office 97) fails to open query - reports error 1109. | ||
|---|---|---|---|
| Submitted: | 27 Jan 2004 2:48 | Modified: | 3 Feb 2004 7:38 |
| Reporter: | Gerhard Scheepers | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S1 (Critical) |
| Version: | MyODBC 3.51.06 | OS: | Windows (WIndows 2000 Prof) |
| Assigned to: | Dean Ellis | CPU Architecture: | Any |
[27 Jan 2004 2:48]
Gerhard Scheepers
[27 Jan 2004 5:00]
Gerhard Scheepers
I have a user on a Compaq D230 Desktop with Windows 2000 Prof and Office 97 Std installed. MySQL Connector/ODBC 3.51 is installed on that PC. The user tries to connect to MySQL server on another machine. The ODBC connection works fine however when the user wants to get data into a Microsoft Query he gets the error "Unknown table 'xxx' in field list. See an extract of the log file below. (Extract from log file) msqry32 54c-2c0 EXIT SQLPrepare with return code 0 (SQL_SUCCESS) HSTMT 00811A28 UCHAR * 0x000A4D68 [ 156] "SELECT chemistry_results.Lab_No, chemistry_results.Sample, chemistry_results.COD, chemistry_results_0.Lab_No\ d\ aFROM lab.chemistry_results chemistry_results_0" SDWORD 156 msqry32 54c-2c0 ENTER SQLExecute HSTMT 00811A28 msqry32 54c-2c0 EXIT SQLExecute with return code -1 (SQL_ERROR) HSTMT 00811A28 DIAG [S1000] [MySQL][ODBC 3.51 Driver][mysqld-4.0.17-nt]Unknown table 'chemistry_results' in field list (1109) How to repeat: This error is repeatable all the time by trying to run a Microsoft query.
[27 Jan 2004 13:30]
Dean Ellis
We need to know what is actually generating the SQL statement in order to determine if the problem is with us, MS Query or human error. The statement itself is invalid, as per the error message, because the table "chemistry_results" is aliased as "chemistry_results_0" in the FROM clause, but referenced as "chemistry_results" in the SELECT.
[27 Jan 2004 22:15]
Gerhard Scheepers
Firstly I must point out that the SQL query was not typed in - MS Query constructed the query itself merely by the user point to certain fields in the database and dragging it accross to the field list. The PC on which MySQL server is installed runs on Windows 2000 Pro and has Office 2000 Std installed. When the exact same query is run on the same table there is no problem at all and the data comes into the query. The PC that connects to the MySQL server with MyODBC 3.51.06 also has Windows 2000 Pro as OS but has Office 97 installed, as noted in the original error report. Another PC that also connects to the MySQL server has a previous version of MyODBC (v2.5) installed and runs Windows 95 as OS. That PC can successfully get data via a Microsoft query. It seem to me that the problem therefore could be caused by the MyODBC 3.51.06 driver in combination with W2K Pro + Office 97 combination. Here is an extract of the log file using a MSquery from the PC where MySQL server is installed (OS = W2K Pro, with Office 2000 Std). (Extract of log file) msqry32 41c-588 EXIT SQLSetStmtOption with return code 1 (SQL_SUCCESS_WITH_INFO) HSTMT 00B91E40 UWORD 4 <SQL_ASYNC_ENABLE> SQLLEN 1 DIAG [01S02] [MySQL][ODBC 3.51 Driver][mysqld-4.0.17-nt]Doesn't support asynchronous, changed to default (502) msqry32 41c-588 ENTER SQLPrepare HSTMT 00B91E40 UCHAR * 0x001808B0 [ 162] "SELECT chemistry_results_0.Lab_No, chemistry_results_0.Sample, chemistry_results_0.COD, chemistry_results_0.Lab_No\ d\ aFROM lab.chemistry_results chemistry_results_0" SDWORD 162 msqry32 41c-588 EXIT SQLPrepare with return code 0 (SQL_SUCCESS) HSTMT 00B91E40 UCHAR * 0x001808B0 [ 162] "SELECT chemistry_results_0.Lab_No, chemistry_results_0.Sample, chemistry_results_0.COD, chemistry_results_0.Lab_No\ d\ aFROM lab.chemistry_results chemistry_results_0" SDWORD 162 msqry32 41c-588 ENTER SQLExecute HSTMT 00B91E40 msqry32 41c-588 EXIT SQLExecute with return code 0 (SQL_SUCCESS) HSTMT 00B91E40 I think the most useful information I can supply you with is to email you the complete log files from both PC's, the ine with the problem and the one where MySQL server is installed. Please let me know if you would want this. Thanks Gerhard
[3 Feb 2004 7:38]
Dean Ellis
The problem (which you hit upon above) is simply that Office 97 needs MyODBC 2.5 because it does not understand the ODBC 3.51 interface, which is what MyODBC 3.51 implements.
[24 Jul 2005 20:18]
gabriel mata
Hi had the same problem width ms excel 2003 and the myodbc 3.51.11-2, to fix it i remove the myodbc 3.51.11-2 and install the old one that i had 3.51.06 ... NICE
[23 Nov 2006 9:18]
Tonci Grgin
No problems detected with 3.51.13 and MS Excel 2003 providing that you use File DSN. When using System/User DSN, crash in MSQRY32 occur as described in Bug#7758.
