forums › forums › SQLyog › Sync tools, Migration, Scheduled Backup and Notifications › Syntax error in from clause
- This topic is empty.
-
AuthorPosts
-
-
September 9, 2003 at 5:59 am #8158BobnzMember
During the import of one db I got the error message …
” [Microsoft][ODBC Microsoft Access Driver] Syntax error in FROM clause.”
Is there some way I can fix this?
Bob
-
September 9, 2003 at 8:21 am #14861RiteshMember
Are you issuing a SQL query to fetch data?
-
September 9, 2003 at 10:55 am #14862BobnzMember
No just using the ODBC import wizard.
Bob
-
September 9, 2003 at 1:09 pm #14863RiteshMember
There is an option in ODBC Import Wizard where you can import data by specifying a SELECT SQL stmt. Anyway, it seems that you are not using the feature.
Can you tell me the steps that you are following?
Better still if you can attach a screenshot when you are getting the error.
HTH
-
September 10, 2003 at 4:15 am #14864BobnzMember
This is a mock up as screen shot only takes top window. I get the error message halfway through the import
I close the error window and the import window looks as it does in the attachment.
I am using the import wizard the way I have for quite a few Dbs and had no problem except where table names need to be cleaned up.
Bob
-
September 10, 2003 at 4:29 am #14865BobnzMember
Edited insert and couldn't reinsert into post.
Bob
-
September 10, 2003 at 5:15 am #14866RiteshMemberQuote:except where table names need to be cleaned up.
Can you explain a little more?
In the last step of the wizard, SQLyog will show you the table name that is currently being imported. Can you find out the table that is giving error?
BTW, can you attach a copy of your database that is giving error, so that we can work on it and fix the bug ( if there are any ) in SQLyog 3.6?
-
September 10, 2003 at 7:00 am #14867BobnzMember
Seems to be tblAccessories, tblMonitor and tblPrinter. I have imported and deleted this DB several times without any problems.
Bob
-
September 11, 2003 at 10:08 am #14868RiteshMember
We were able to import the data without any problem. We have Office 2K.
Try, dropping the above mentioned tables in the MySQL server and re-import it from Access.
-
September 12, 2003 at 6:02 am #14869BobnzMember
Ok I have imported all tables in the database. However I had to go into the access version and rename tables and fields, remove spaces in names and other characters that sqlyog didn't like. None of which I have had to do before when importing to mysql.
I have two linux boxes both running mysql. Once a DB has been imported successfully I import a copy on to the testing server and run the scripts which will be run by users and admin. The way this import has gone I wont be able to test any scripts against it because of the different table and field names. Is there a setting I haven't configured on the testing server that causes this difference in the import process?
Bob
-
September 12, 2003 at 7:36 am #14870RiteshMemberQuote:The way this import has gone I wont be able to test any scripts against it because of the different table and field names. Is there a setting I haven't configured on the testing server that causes this difference in the import process?
Can you explain a little more?
-
September 12, 2003 at 11:00 am #14871BobnzMember
I have had to remove all spaces in field names eg. “I P Address” becomes “IPAddress” and other field names such as “Memory(M:cool:” (sqlyog error said it was undefined function) becomes MemoryMB one field name had a “?” that had to go. and various others….
Bob
-
September 12, 2003 at 3:07 pm #14872RiteshMember
Which version of Access you have?
I think there is some problem with your ODBC driver.
-
September 12, 2003 at 8:43 pm #14873BobnzMember
I'm using Access 2000 (9.0.3821 SR-1)
Bob
-
September 13, 2003 at 4:47 am #14874BobnzMember
I have uninstalled sqlyog from the WIN2k machine and installed it on a laptop and connected that to the server and imported an original copy of the DB (with all the odd field names) with the same results. I thought I had had success but the first import was the amended DB not the original. When I tried the original DB the import process fell over with the error I first posted. How likely is it that two successive PC's have corrupt ODBC?
Bob
-
-
AuthorPosts
- You must be logged in to reply to this topic.