Access crash

Hi

I have a few Access applications (in .mdb files) that work with MySQL
ODBC-linked tables.
Suddenly from two PCs (both with Windows 2000, Access 2003, latest
MDAC and MS Jet versions) the tables are impossible to be re-linked
through the MySQL ODBC driver, using the "link manager".
I tried to install the latest ODBC drivers, but the result is the
same: when I arrive at the "link manager", I select the new ODBC
driver, I select "Ok", instead of having the form where I can select
the tables of the destination database, the Access program crashes.
And this happens with every .mdb file, even an empty one.
Both PCs are of recent, careful operating system reinstallation.

Can anybody please indicate me a possible solution ?

Thank you

Enrico


--
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: Access crash

Enrico Nicolis wrote:

> Hi
>
> I have a few Access applications (in .mdb files) that work with MySQL
> ODBC-linked tables.
> Suddenly from two PCs (both with Windows 2000, Access 2003, latest
> MDAC and MS Jet versions) the tables are impossible to be re-linked
> through the MySQL ODBC driver, using the "link manager".
> I tried to install the latest ODBC drivers, but the result is the
> same: when I arrive at the "link manager", I select the new ODBC
> driver, I select "Ok", instead of having the form where I can select
> the tables of the destination database, the Access program crashes.
> And this happens with every .mdb file, even an empty one.
> Both PCs are of recent, careful operating system reinstallation.
>
> Can anybody please indicate me a possible solution ?
>
That's harsh.

Does the 'linked table manager' only crash for MyODBC, or does it crash
for other ODBC data sources as well? I don't suppose you've got a legacy
SQL Server system that you can test connecting to? :)

What version of MyODBC are you using? You have to tread carefully with
recent versions - the best bet for you is the version that isn't yet
released. A link has been posted in the list ( subject: We need help
testing MyODBC 3.51.12 ). Direct link to driver:
ftp://ftp.mysql.com/pub/mysql/hidden/connectors/odbc/3.51.12 /MyODBC-3.51.12-win32.exe

As for solutions, if you've got the above driver and it's still
crashing, try scanning through the MyODBC list ( last 2 weeks or so )
for a previous post on relinking tables - some code was posted that
refreshes linked tables - I assume this could be modified to create a
new link. This may or may not work, of course, but that's where I'd
start if you linked table manager won't do it for you. From memory the
subject will NOT mention linking tables - the thread went slightly
off-topic - so you'll have to do a lot of reading to find it. Sorry.

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

Re: Access crash

At 01.09 27/07/2005, you wrote:
>Enrico Nicolis wrote:
>
> > Hi
> >
> > I have a few Access applications (in .mdb files) that work with MySQL
> > ODBC-linked tables.
> > Suddenly from two PCs (both with Windows 2000, Access 2003, latest
> > MDAC and MS Jet versions) the tables are impossible to be re-linked
> > through the MySQL ODBC driver, using the "link manager".
> > I tried to install the latest ODBC drivers, but the result is the
> > same: when I arrive at the "link manager", I select the new ODBC
> > driver, I select "Ok", instead of having the form where I can select
> > the tables of the destination database, the Access program crashes.
> > And this happens with every .mdb file, even an empty one.
> > Both PCs are of recent, careful operating system reinstallation.
> >
> > Can anybody please indicate me a possible solution ?
> >
>That's harsh.
>
>Does the 'linked table manager' only crash for MyODBC, or does it crash
>for other ODBC data sources as well? I don't suppose you've got a legacy
>SQL Server system that you can test connecting to? :)

From the same PCs, I can successfully link Access tables to an SQL
server: the list of the sql server tables correctly appears in the dialog box.

>What version of MyODBC are you using? You have to tread carefully with
>recent versions - the best bet for you is the version that isn't yet
>released. A link has been posted in the list ( subject: We need help
>testing MyODBC 3.51.12 ). Direct link to driver:
>ftp://ftp.mysql.com/pub/mysql/hidden/connectors/odbc/3.51.1 2/MyODBC-3.51.12-win32.exe

Even with this new version, the problem isn't solved: the "link
tables" dialog box never appears, and access crashes.

>As for solutions, if you've got the above driver and it's still
>crashing, try scanning through the MyODBC list ( last 2 weeks or so )
>for a previous post on relinking tables - some code was posted that
>refreshes linked tables - I assume this could be modified to create a
>new link. This may or may not work, of course, but that's where I'd
>start if you linked table manager won't do it for you. From memory the
>subject will NOT mention linking tables - the thread went slightly
>off-topic - so you'll have to do a lot of reading to find it. Sorry.

This is a good solution, but there is also a workaround (taken from
http://bugs.mysql.com/bug.php?id=9932) that lets the "link tables"
dialog box magically reappear.
The suggestion is to change the msjet40.dll library in two places:
- C:\WINNT\system32\dllcache
- C:\WINNT\system32
reinstalling the old version (4.0.8618.0) at its place. The
substitution should be done in this order, to override the file
protection of the operating system.
And this works !

Thank you for your help

Enrico


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