The returned value for accessing the database using MYSQL odbc 3.51 is missing.

The tutorial for helping customers (www.bkjia.com) is missing when using MYSQL odbc 3.51 to access the database with an unmeasurable BUG. The driver should be updated in a timely manner.

Idle talk ,:

1. The value stored in the database is "Burma"

2. using mysql odbc driver of MYSQL 3.51 5.0 to access MYSQL database is worth the "Boolean" value obtained after encoding and conversion of the original character "too many characters", and part of the data is lost.

 

3. use the mysql odbc driver of Version 5.1 to access the MYSQL 5.0 database. It is worthwhile to obtain the value of "Burma" After encoding and conversion from the original character "ç ¸ ƒ å ° ", complete data.

====================

Summary: database-driven new versions are always released with the release of new versions of data. Therefore, you must use drivers of different versions for different databases.

Although ODBC database access encoding is much less, it must be followed.

In addition, the underlying layer of MYSQL 5.0 seems to have changed a lot. The original characters read by the two ODBC drivers are completely different.