Not the regular ACcess ODBC cerror problem.

------=_NextPart_000_000B_01C530C9.41E9FAA0
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hello, I don't know where else to ask. it's been about 5 months. I
actually gave up, but now that I have some free time I started pursuing
this issue again.
I've successfully connected my Microsoft Access front End to a MySQL
database using ODBC.
I followed all the rules that I have seen posted all over the web. My
connection works,.
The problem is that after 10 minutes I get an ODBC Failed error. Most of
the time, I just close the fomr and reopen and it works again, but
soemtiems the error repeats until I have to close Access and reopen.
The good news is that I usually can get my work done,. its just
annoying to see the fail error all the time and sometimes get shuit out
of Access until restart. I have followed all suggestions and still this
happens. I think the suggestions are actually to get you connected.. im
just having a problem staying connected I guess.. my exact problem is
listed below. please point me in the right direction if you can. Thank
you so much! In advance.


I have a form that uses a linked table as it's data source. It is linked
to MYSQL table via ODBC (and I have "return matching rows" enabled).
I can open up the form & make changes etc.. and change records.. But if
I don't touch it for awhile, I get the following error:

ODBC--call fialed.
Lost connection to MySql server during query (#2013)

Soemtiems I can just close the form and reopen it and it works.. But
other tiems,
If I open up the form right away, and then walk away from the computer
for about 10 minutes, when i come back and try to use it, i get an error
saying "No current Record"
I press "OK", but then i get anopther error immediately saying: "ODBC--
Clall Failed"

I press OK to that one, and get yet another:
"Object invalid or no longer set"

And it repeats between "Failed" aND "nO LONGER sET" UNTIL IT CRASHES. *
well soemtiems it doesnt crash.

------=_NextPart_000_000B_01C530C9.41E9FAA0--

Re: Not the regular ACcess ODBC cerror problem.

Dan wrote:

>Hello, I don't know where else to ask. it's been about 5 months. I
>actually gave up, but now that I have some free time I started pursuing
>this issue again.
>I've successfully connected my Microsoft Access front End to a MySQL
>database using ODBC.
>I followed all the rules that I have seen posted all over the web. My
>connection works,.
>The problem is that after 10 minutes I get an ODBC Failed error. Most of
>the time, I just close the fomr and reopen and it works again, but
>soemtiems the error repeats until I have to close Access and reopen.
>The good news is that I usually can get my work done,. its just
>annoying to see the fail error all the time and sometimes get shuit out
>of Access until restart. I have followed all suggestions and still this
>happens. I think the suggestions are actually to get you connected.. im
>just having a problem staying connected I guess.. my exact problem is
>listed below. please point me in the right direction if you can. Thank
>you so much! In advance.
>
>
>I have a form that uses a linked table as it's data source. It is linked
>to MYSQL table via ODBC (and I have "return matching rows" enabled).
>I can open up the form & make changes etc.. and change records.. But if
>I don't touch it for awhile, I get the following error:
>
>ODBC--call fialed.
>Lost connection to MySql server during query (#2013)
>
>Soemtiems I can just close the form and reopen it and it works.. But
>other tiems,
>If I open up the form right away, and then walk away from the computer
>for about 10 minutes, when i come back and try to use it, i get an error
>saying "No current Record"
>I press "OK", but then i get anopther error immediately saying: "ODBC--
>Clall Failed"
>
>I press OK to that one, and get yet another:
>"Object invalid or no longer set"
>
>And it repeats between "Failed" aND "nO LONGER sET" UNTIL IT CRASHES. *
>well soemtiems it doesnt crash.
>
>
>
I had errors along these lines a very long time ago. I'm pretty sure I
fixed it with a patch I found on Microsoft's site for an identical
problem when connecting to Oracle. I haven't come across it for quite
some time indeed, and I'm pretty sure it's included in other patches,
such as Office service packs, MDAC updates, etc. From memory, it was a
Microsoft Jet Engine problem ( Jet is their database engine in Access ).

I also had a workaround for a while: open a form and hide it, and put
some code in it's on_timer property that periodically ( once every
10,000 clicks ) does a simple query against MySQL, to keep the
connection alive. I did a couple of queries on things like the query
cache hit rate, and made a status monitor in the status bar. But this is
no longer necessary now that Microsoft seem to have fixed the issue.

Check you have the most recent version of everything. Sorry I can't be
more specific. Search *way* back through the mailing list archives for
more discussion. I think I even posted a link to the patch, but this may
have been moved by now anyway.

Dan

--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: dkasak@nusconsulting.com.au
website: http://www.nusconsulting.com.au

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org