Cannot import binary data > 1M into MySQL BE

[thhui]

By further reading of the following link and consolidation of previous setting recommended.



http://dev.mysql.com/doc/refman/5.1/...arameters.html

I summarized the following findings:-

The Access Mysql-ODBC connection parameter supplied should be enabled as ticking the following options

Set the Advanced Tab of the mysql odbc connector options as ticking:-
Allow Big Results
Change BIGINT Column To int
Limit column size to signed 32-bit range
Enable Dynamic Cursor
Return Matching Rows
Read Options from my.cnf

This is just the same as the options number stated above.
Being a graphical implementation of the recommended option number.

[thhui]

There are OLE bug issues in mysql odbc connector in access to deal with blog data.

Access 2007 or 2010 has a new attachement field which overcome the issues of OLE.

I use alternative JDBC-Mysql driver which is faultless in storing over 1M blob data.
PhpMyadmin also could do the same work.

Conclusion:-
It is only ODBC-Mysql Connector to have fault with Access <2007 to have OLE bug issues in dealing with blob data.

[thhui]

By adopting the coding in the article of Accessing MySQL BLOB columns using Visual Basic 6 or MS Access,
http://dev.mysql.com/tech-resources/...-handling.html

I succeed in Access ODBC using ADO2.8 sending the blob data over 1M to mysql server. (max_allowed_packet of mysql server changed to 3M)

Do not use the default OLE type insert.