Jet and MySQL

[alecjames1]

I have an Access 2K front end running on a Windows 2000 computer linked
to a MySQL database as a backend.
Recently after my Windows is updated I find that Access will not link
to MySQL. I have found that if I replace the msjet4.dll with an older
version everything works fine.
The problem is that my clients are getting problems whenever Windows
updates. With WXP this is not a problem only with W2K.
Alec

[dbahooker]

you should be using ACCESS DATA PROJECTS against MSDE instead.

much better performance; none of the headaches

[Larry Linson]

<al********@hotmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...

I have an Access 2K front end running on a Windows 2000 computer linked
to a MySQL database as a backend.
Recently after my Windows is updated I find that Access will not link
to MySQL. I have found that if I replace the msjet4.dll with an older
version everything works fine.
The problem is that my clients are getting problems whenever Windows
updates. With WXP this is not a problem only with W2K.

This is not a problem with which I am familiar and I no longer have any
computers running Windows 2000, so all I can suggest is that perhaps there
is some incompatibility with the most recent Service Pack or update to
msjet4.dll, Windows 2000, and the MyODBC drivers.

Have you searched the Knowledge Base at http://support.microsoft.com? That
would be the best place to start looking.

Do I understand correctly that replacing msjet4.dll with an earlier version
is a workaround that allows connecting and does not appear to cause other
problems?

Larry Linson
Microsoft Access MVP

[paradigm]

The problem is with Access 2K and Windows 2K. The msjet4.dll does not allow
connection to a mysql database. Replacing it with and older version fixes
the problem and does not appear to have any detrimental effects. Everytime
W2K does an update we have to replace the msjet4.dll file. This has be be
done in a particluar sequence, deleting it from dllcache first and then
from system32.
Alec
"Larry Linson" <bo*****@localhost.not> wrote in message
news:%aH3f.45282$HM1.26698@trnddc04...

<al********@hotmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...

I have an Access 2K front end running on a Windows 2000 computer linked
to a MySQL database as a backend.
Recently after my Windows is updated I find that Access will not link
to MySQL. I have found that if I replace the msjet4.dll with an older
version everything works fine.
The problem is that my clients are getting problems whenever Windows
updates. With WXP this is not a problem only with W2K.

This is not a problem with which I am familiar and I no longer have any
computers running Windows 2000, so all I can suggest is that perhaps there
is some incompatibility with the most recent Service Pack or update to
msjet4.dll, Windows 2000, and the MyODBC drivers.

Have you searched the Knowledge Base at http://support.microsoft.com? That
would be the best place to start looking.

Do I understand correctly that replacing msjet4.dll with an earlier
version is a workaround that allows connecting and does not appear to
cause other problems?

Larry Linson
Microsoft Access MVP

[David W. Fenton]

"paradigm" <al********@hotmail.com> wrote in
news:ft*****************@newsfe4-gui.ntli.net:

The problem is with Access 2K and Windows 2K. The msjet4.dll does
not allow connection to a mysql database. Replacing it with and
older version fixes the problem and does not appear to have any
detrimental effects. Everytime W2K does an update we have to
replace the msjet4.dll file. This has be be done in a particluar
sequence, deleting it from dllcache first and then from system32.

Have you checked MySQL forums for this?

I don't understand why a different version of Jet4 would cause the
MyODBC drivers to cease working correctly. Perhaps the MyODBC
project is working on a fix?

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

[paradigm]

i have a site with more than 150 clients running from a mysql server
performance is good, it is easy to maintain and was cheap to set up

<db*******@hotmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...

you should be using ACCESS DATA PROJECTS against MSDE instead.

much better performance; none of the headaches