Loosing data with ODBC-connection to MySQL

[tomcat 155]

Hi,
I'm developing an LabVIEW application where i need to store pictures and large amounts of measurement data in LONGBLOB-fields in a MyISAM tables in MySQL database. Connection to MySQL is done with MySQL ODBC driver 3.51.06 using LabVIEW 7.0 and Database Connectivity Toolkit.
For small amounts of data like a jpg-picture of 70 kb there is no problem, but with larger amounts of data like an jpg-picture of 150 kB, data is simply not stored in the database. Also larger measurement data blocks of approx. 600 kb will not store. When cutting datablocks to about 130 kb it works fine again. I presumed this was a ODBC driver problem, but now I'm not sure, is there maybe a problem with the Databse Connectivity Toolkit, or am I simply
out of specifications anywhere ??

[Crystal]

No size limitations are imposed by LabVIEW or the Database Toolkit VIs themselves. However, as you know there are many different SW layers involved. The Database Toolkit VIs go through ActiveX and then through the ODBC driver. Are you getting any kind of errors or is the data just getting truncated? Usually the error code can give you an idea of where the limitation occurs.

[tomcat 155]

Crystal,

Thanks for answering on my question, not many users semms to be using the LabVIEW-Database Connectivity-MySQL configuration !?, as for Your question, the following error message is generated by the "DB Tools Insert Data" vi:

"Cmd Execute.vi->DB Tools Insert Data.vi->Information Administrator.viException occured in Microsoft OLE DB Provider for ODBC Drivers, [MySQL][ODBC 3.51 Driver][mysqld-4.1.0-alpha-max]Lost connection to MySQL server during query. in Rec Create - Command.vi->Cmd Execute.vi->DB Tools Insert Data.vi->Information Administrator.vi"

In most cases i don´t use this vi, normally I use the "Connection Execute" vi to generate SQL commands, in any case the problems remains regardless of how the SQL commans is generated.

Any
ideas of why the exception occurs and connection is lost??

[Crystal]

That error is coming from the mySQL ODBC driver. However, it's unclear as to whether the connection is dropped by the driver because of a problem with the command, a problem with the returned data, or if the connection is dropped by any other means. I think the phrase "mysqld-4.1.0-alpha-max" might be important. It almost sounds like an alpha version of the next driver is being used. I think only the guys at mySQL would know why that is tacked onto the error message and what component that is.

[tomcat 155]

Thanks Crystal,

I will try to get some information from the MySQL community!