Access + MySQL = ODBC-call failed... sometime

[Yannick Turgeon]

Hello all,

I'm using:
- A97 (front-end)
- MySQL drivers 3.51
- MySQL 4.0.18 (back-end)

I've got a MySQL table connected to an Access DB throw an ODBC link. When I
connect to this table, no matter the query, a connection is created in
MySQL. Initialy, this connection stayed opened 8 hours (default. controled
by a MySQL variable "wait_timeout") . We had trouble with this (too much
connections opened at the same time) so we get this down to 250 seconds.
Now, when whe create a connection, it is being closed after 250 seconds,
then the next call made from access to this table (for the same user) will
invariably produce an "ODBC-call failed" error message. Then the next call
is OK... for the next 250 seconds.

Anyone has clue on how to solve this. In my test, I do not use specific
recordset but instead, the DLookUp function in Access. So there is no "no
closed recordset" consideration here.

Thanks for your time.

Yannick

PS. Didn't find a MySQL newsgroup on my news server... curious. I'll search
on the web.

[Steve Jorgensen]

I understand that this is a bug in Access 2002 (and probably 2003) with ODBC
links to just about anything except MS SQL Server or Oracle.

On Fri, 4 Jun 2004 11:44:44 -0400, "Yannick Turgeon" <no****@nowhere .com>
wrote:

Hello all,

I'm using:
- A97 (front-end)
- MySQL drivers 3.51
- MySQL 4.0.18 (back-end)

I've got a MySQL table connected to an Access DB throw an ODBC link. When I
connect to this table, no matter the query, a connection is created in
MySQL. Initialy, this connection stayed opened 8 hours (default. controled
by a MySQL variable "wait_timeout") . We had trouble with this (too much
connections opened at the same time) so we get this down to 250 seconds.
Now, when whe create a connection, it is being closed after 250 seconds,
then the next call made from access to this table (for the same user) will
invariably produce an "ODBC-call failed" error message. Then the next call
is OK... for the next 250 seconds.

Anyone has clue on how to solve this. In my test, I do not use specific
recordset but instead, the DLookUp function in Access. So there is no "no
closed recordset" consideration here.

Thanks for your time.

Yannick

PS. Didn't find a MySQL newsgroup on my news server... curious. I'll search
on the web.

[David W. Fenton]

Steve Jorgensen <no****@nospam. nospam> wrote in
news:nl******** *************** *********@4ax.c om:

I understand that this is a bug in Access 2002 (and probably 2003)
with ODBC links to just about anything except MS SQL Server or
Oracle.

How exactly does this cause Access97 to break (which is what the
original poster is using)?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Steve Jorgensen]

On Fri, 04 Jun 2004 17:52:58 GMT, "David W. Fenton"
<dX********@bwa y.net.invalid> wrote:

Steve Jorgensen <no****@nospam. nospam> wrote in
news:nl******* *************** **********@4ax. com:

I understand that this is a bug in Access 2002 (and probably 2003)
with ODBC links to just about anything except MS SQL Server or
Oracle.

How exactly does this cause Access97 to break (which is what the
original poster is using)?

Oops - my bad, then. Sorry about that.