I have a (dumb!) program that performs SELECT statements with a quote around the table and the fieldname; see the portion from the trace log below: Cardfive fffe35e1:fffed875 EXIT SQLExecDirect with return code -1 (SQL_ERROR) HSTMT 0x00cf17ac UCHAR * 0x00ae62ac [ 363] "SELECT `telstrasaturn`.`AutonumberedKey`,`telstrasaturn`.`ID`,`telstrasaturn`.`Stat us`,`telstrasaturn`.`ExtendedStatus`,`telstrasaturn`.`FIRSTNAME`,`telstrasat urn`.`SURNAME`,`telstrasaturn`.`DIVISION`,`telstrasaturn`.`LOCATION`,`telstr asaturn`.`LOC_NO`,`telstrasaturn`.`PICTURE`,`telstrasaturn`.`EXPDATE`,`telst rasaturn`.`PRNREC` FROM "telstrasaturn" FOR UPDATE " SDWORD 363 DIAG [42000] [TCX][MyODBC]You have an error in your SQL syntax near '"telstrasaturn" ' at line 1 (1064) -- What workaround do I have for this? The 'FOR UPDATE' clause also seems to be at fault; if I query a MySQL table "SELECT * FROM TABLE FOR UPDATE' i get an sql syntax error "near FOR UPDATE" -- does this imply MySQL does not yet have support for this? Is there anyway for MyODBC, or MySQL server to rid SELECT statements it parses of 1) the uncessary quotes (basically replace '.' to . ) 2) the FOR UPDATE clause The UPDATE locking is not a necessity in the application; Win9x Card printing software which uses ONLY odbc as a connection method. Thanks, Siggy
