MySql server Win7 32, ODBC connector causing large tables to crash ODBC connector

does the table have a primary key field?
especially for append operations this should work fine, at least I could work just fine even on large tables (10 million rows) ...

now, what do you call "large" tables?
what type of tables? MyISAM, InnoDB, something else?

The Source table doesn't have a primary key but the destination table does. Its the autonum.
If we append a table of say 3000 records it works fine. A table of say 70,000 records causes the ODBC to crash.
They are linked ODBC tables  using the above odbc driver and created in MS Access 2000
As for MyISAM, InnoDB
Please explain the difference. I just created the tables in MSACCESS, exported the to MySQL and linked them back, as it was easier to use the graphical interface in MSAccess

Pls reply to my post too

>As for MyISAM, InnoDB
>Please explain the difference.
it's the table storage engines:
http://dev.mysql.com/doc/refman/5.1/en/storage-engines.html
it may impact the performance ...

tables stored as MYISAM
Set max_allowed_packet to 16M and same error...

Try increasing it to 32M or 64M.
Also you have to set max_allowed_packet into the my.cnf file and restart the database.
Can you post the error you are getting?

Regards,
   Tomas Helgi

and 32M
max_allowed_packet = 32M
The size of the table being appended is a 2Meg Text file imported to a table  and the table to which it is appended is about 800Meg

Unfortunately access just returns a general error with inserting table - no specific error no.
A clue to solution. When I was using the older version 3 ODBC driver and had the database stored in a Linux MySql server this problem did not exist.
Is there a way I can run the query from within MySql & call it from MSaccess? I will have to pass a single parameter to the query. I need a simple insert query.

I need an automated system for MSAccess to process the queries ...

to automate SQL queries, you don't need ms access.
you can scheduled SQL scripts with MySQL easily also:
http://dev.mysql.com/doc/refman/5.1/en/events-overview.html

and if it's based on human input (button click), you could code it all inside a stored procedure, and just run that one ...

But how would I call the MYSQL query from within Access VB

Hi!

If you are inserting into a MySQL table  from Access you will need to first create a Linked Table through the MySQL ODBC driver and then you can use the ADO Insert method in the VB.
Same goes for  any other database table.

Regards,
     Tomas Helgi

you can do sql over ado:
http://dev.mysql.com/doc/connector-odbc/en/connector-odbc-examples-programming-vb-ado.html

I want to call a stored Query from Access

what kind of stored query?
you can translate them into the mysql corresponding code, which will then run on the mysql server, running better...

Want to sort out queries failing for large tables....
Btw, tried
max_allowed_packet. of 128M
Same error

Exact error in Access: 3155 ODBC -- insert on linked table 'name' failed

Yes, It only fails on big tables- see above please