Trouble connecting to mysql databases to link tables

[Tracey]

I have a Mysql database hosted on a remote server. Previously, I could
always connect to those databases using the 3.51 ODBC connector and
linking the tables in Access. The benefit of this is that I can view
the data from my desktop, export it to spreadsheets if necessary and
print labels.

I guess because of a Mysql upgrade by my host, the 3.51 connector
stopped working (the password hash problem), so I upgraded to the 5.*
ODBC connector (beta). That got me connected, but I can't view the only
table in the database because I get this error:

ODBC -- call failed.

[MySQL][MyODBC 5.00.6][MySQL] 1142 SELECT command denied to user
(myusername)@(myisp) for table 'STATISTICS' #1142

I didn't even KNOW I had a table called "statistics," although I guess
it's a log or something. I was trying to link a table called "signups"
that's in the database.

I know my login info is correct, because I've been able to open the
database and edit this table using a free GUI called SQLYog.

I don't have command-line access to my databases, so any queries have
to be run (I assume) from phpMyAdmin.

Any suggestions? And please talk to me like I'm a five-year-old,
because when it comes to this stuff, I am. :)
Thanks,

Tracey

[abejer]

If it worked before, then I suspect your ODBC driver may not be
compatible with the new version of MySQL. Also, never use a beta
edition in production mode. Instead of version 5, get the latest
version of 3.51 (3.51.12) from here:

http://dev.mysql.com/downloads/connector/odbc/3.51.html

Alexandre Bejerman
Montreal, Canada
Tracey wrote:

I have a Mysql database hosted on a remote server. Previously, I could
always connect to those databases using the 3.51 ODBC connector and
linking the tables in Access. The benefit of this is that I can view
the data from my desktop, export it to spreadsheets if necessary and
print labels.

I guess because of a Mysql upgrade by my host, the 3.51 connector
stopped working (the password hash problem), so I upgraded to the 5.*
ODBC connector (beta). That got me connected, but I can't view the only
table in the database because I get this error:

ODBC -- call failed.

[MySQL][MyODBC 5.00.6][MySQL] 1142 SELECT command denied to user
(myusername)@(myisp) for table 'STATISTICS' #1142

I didn't even KNOW I had a table called "statistics," although I guess
it's a log or something. I was trying to link a table called "signups"
that's in the database.

I know my login info is correct, because I've been able to open the
database and edit this table using a free GUI called SQLYog.

I don't have command-line access to my databases, so any queries have
to be run (I assume) from phpMyAdmin.

Any suggestions? And please talk to me like I'm a five-year-old,
because when it comes to this stuff, I am. :)
Thanks,

Tracey

[abejer]

If it worked before, then I suspect your ODBC driver may not be
compatible with the new version of MySQL. Also, never use a beta
edition in production mode. Instead of version 5, get the latest
version of 3.51 (3.51.12) from here:

http://dev.mysql.com/downloads/connector/odbc/3.51.html

Alexandre Bejerman
Montreal, Canada
Tracey wrote:

I have a Mysql database hosted on a remote server. Previously, I could
always connect to those databases using the 3.51 ODBC connector and
linking the tables in Access. The benefit of this is that I can view
the data from my desktop, export it to spreadsheets if necessary and
print labels.

I guess because of a Mysql upgrade by my host, the 3.51 connector
stopped working (the password hash problem), so I upgraded to the 5.*
ODBC connector (beta). That got me connected, but I can't view the only
table in the database because I get this error:

ODBC -- call failed.

[MySQL][MyODBC 5.00.6][MySQL] 1142 SELECT command denied to user
(myusername)@(myisp) for table 'STATISTICS' #1142

I didn't even KNOW I had a table called "statistics," although I guess
it's a log or something. I was trying to link a table called "signups"
that's in the database.

I know my login info is correct, because I've been able to open the
database and edit this table using a free GUI called SQLYog.

I don't have command-line access to my databases, so any queries have
to be run (I assume) from phpMyAdmin.

Any suggestions? And please talk to me like I'm a five-year-old,
because when it comes to this stuff, I am. :)
Thanks,

Tracey

[abejer]

If it worked before, then I suspect your ODBC driver may not be
compatible with the new version of MySQL. Also, never use a beta
edition in production mode. Instead of version 5, get the latest
version of 3.51 (3.51.12) from here:

http://dev.mysql.com/downloads/connector/odbc/3.51.html

Alexandre Bejerman
Montreal, Canada
Tracey wrote:

I have a Mysql database hosted on a remote server. Previously, I could
always connect to those databases using the 3.51 ODBC connector and
linking the tables in Access. The benefit of this is that I can view
the data from my desktop, export it to spreadsheets if necessary and
print labels.

I guess because of a Mysql upgrade by my host, the 3.51 connector
stopped working (the password hash problem), so I upgraded to the 5.*
ODBC connector (beta). That got me connected, but I can't view the only
table in the database because I get this error:

ODBC -- call failed.

[MySQL][MyODBC 5.00.6][MySQL] 1142 SELECT command denied to user
(myusername)@(myisp) for table 'STATISTICS' #1142

I didn't even KNOW I had a table called "statistics," although I guess
it's a log or something. I was trying to link a table called "signups"
that's in the database.

I know my login info is correct, because I've been able to open the
database and edit this table using a free GUI called SQLYog.

I don't have command-line access to my databases, so any queries have
to be run (I assume) from phpMyAdmin.

Any suggestions? And please talk to me like I'm a five-year-old,
because when it comes to this stuff, I am. :)
Thanks,

Tracey

[Tracey]

Well, looks like you're right. I'd been told by someone in the mySql
forums that I'd need to run a 5.* client to get around a password
hashing incompatibility that was introduced in mysql 4.*, but that
version of the 3.51 client you pointed me to works like a charm.
Thanks!

Tracey