Re: MS Access frontend slow SOLUTION
SOLUTION!
i've had the same problem already with just a single table, just jumping to the last or "new entry" row needed about 15 seconds for a table of 13.000 rows. another table with 370.000 rows was just unusable. so it's not the JOIN.
one hint was to check if dns reverse lookup of the ip address is a problem, so i set up a dedicated dns on the mysql server for the net. that worked perfectly but didn't solve anything.
another hint i got from somewhere here was to switch back to version 3.51.9 of the mysql odbc driver, did that, and guess what: some tables were fast!
and the difference between a fast an a slow table was the odbc connect "OPTION" parameter. the fast tables were the ones linked with 3.51.9, containing "OPTION=2347". the slow ones were those linked with 3.51.12, containing "OPTION=40" -- it seems access did not update this parameter according to the dsn configuration changes i tried before.
so i finally tried to create the odbc connect string manually using "OPTION=2347" with 3.51.12 and everything's fine now! jumping to EOT now needs <2 seconds for the 370.000 row table.
now i'm curious what 2347 means in terms of connection flags... ;-)
michael
Edited 1 time(s). Last edit at 02/13/2006 10:29AM by Michael Balzer.
Subject
Views
Written By
Posted
6106
February 03, 2006 09:22AM
2451
February 03, 2006 11:45AM
2980
February 03, 2006 12:55PM
Re: MS Access frontend slow SOLUTION
2639
February 13, 2006 10:28AM
2328
February 13, 2006 11:15AM
2084
February 15, 2006 11:48AM
2453
February 17, 2006 07:04AM
2447
February 17, 2006 06:28AM
2352
February 17, 2006 07:09AM
3127
February 22, 2006 04:30PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.