Problems with MS Access and MyODBC

Hello!

I have a VB6 program (haven´t written it myself) that uses an access2000
compatible database as a customer register. I have to change the
database so that it will use the customer register from a mysql
database. Database has about 4800 customers. I have configured the
database to export the customer table from a mysql using the myodbc 3.51
driver (File->Get External Data->Link Tables), and it works fine for a
moment, but after a while the vb6 program crashes. When I try handling
the mySQL table again with MS Access it pops up "ODBC --call failed.
(...) MySQL server has gone away (#2006)"
I´m not able to change the VB6 code nor the mySQL server settings.

Does this have something to do with keeping the connection alive or what
("wait-timeout")? MySQL server is 4.1.20-log.

Thanks
-Pasi, Finland

--
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

Re: Problems with MS Access and MyODBC

Pasi Valkeila wrote:
> Hello!
>
> I have a VB6 program (haven´t written it myself) that uses an
> access2000 compatible database as a customer register. I have to
> change the database so that it will use the customer register from a
> mysql database. Database has about 4800 customers. I have configured
> the database to export the customer table from a mysql using the
> myodbc 3.51 driver (File->Get External Data->Link Tables), and it
> works fine for a moment, but after a while the vb6 program crashes.
> When I try handling the mySQL table again with MS Access it pops up
> "ODBC --call failed. (...) MySQL server has gone away (#2006)"
> I´m not able to change the VB6 code nor the mySQL server settings.
>
> Does this have something to do with keeping the connection alive or
> what ("wait-timeout")? MySQL server is 4.1.20-log.

I used to have this problem a very long time ago. There was a patch from
Microsoft to fix it - it also fixed a problem with Access crashing when
connected to Oracle. To be honest I don't know where the patch is
anymore. I posted details against the 'application-specific tips' on the
MySQL webpage:
http://dev.mysql.com/doc/refman/5.0/en/myodbc-usagenotes-app tips.html#myodbc-usagenotes-apptips-microsoft-access
but I've just had a look there ( after searching for 10 minutes to find
this page ), and my post is no longer there. Perhaps this issue has been
fixed in a later version of MDAC? Anyway, check you have the latest
version of MDAC and service packs and things, and also make sure you do
one of the work-arounds listed on http://bugs.mysql.com/bug.php?id=9932
( I take the 'msaccess.exe.local' one ). Also make sure you're
implementing all the other workarounds mentioned on that 1st page I
posted - you have to jump through hoops somewhat to get Access to work
with MySQL.

--
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