ODBC Connection to MySQL

[Vic Spainhower]

Hello,

I have setup an ODBC Connection to a MySQL database (driver version is 3.51)
but when I setup the link in MS Access 2002 some of the tables will show
#Name? in all of the fields, some will show #Deleted in all of the fields
and some will work (except I can't update them). One of the table that I
get #Name? is only 2 columns created with the following SQL:

CREATE TABLE `login` (
`loginName` varchar(20) NOT NULL default '',
`loginTime` datetime NOT NULL default '0000-00-00 00:00:00',
PRIMARY KEY (`loginName`,`loginTime`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

On the #Name? ones I also get the message ODBC Call Failed with the
following message. The MySQL database is on my local machine which is
confusing because some of the table display the data correctly which
indicates it should not be a connection problem.

ODBC - call failed. (Error 3146)
Using an ODBC connection, you tried to perform an operation on data in an
ODBC data source. This error may occur when the ODBC data source is on a
network drive and you are not connected to the network. Make sure the
network is available, and then try the operation again.



Thanks,



Vic

 

[Vic Spainhower]

Hello,

Just in case someone else runs into this, I was able to resolve this by
installing an older ODBC driver (3.51.09) and replacing the current driver
version 3.51.11. After dropping back to the older version all of the
#Name? problems went away but I continued to have a couple of tables that
would only show #Deleted in all of the fields. I was able to resolve this
by changing the key field in the MySQL table from BIGINT to INTEGER.
Supposedly, Access can handle the BIGINT fields as there is an option in the
driver (Change BIGINT to INTEGER) but for what ever reason it wasn't
working.

Vic