(Guessing Only): There could be some minor corruptions in the Tables (when
they were in the original database) that slow down the Query. When
the Tables were moved, the corruptions might have been fixed in going into
the 2nd database and you Query runs faster.
I had a case where a Front-End got corrupted but everything still work
correctly except Queries took a long time to execute. Compact & Repair
didn't help. I finally create a new blank database and import all Objects
from the corrupted database to the new database and the Queries run in about
a tenth of the time it took in the corrupted database.
--
HTH
Van T. Dinh
<mj**********@yahoo.com> wrote in message
news:kD*********************@newssrv26.news.prodig y.com...
I had an .mdb which conatains a dozen or so tables,
and some relatively conmplex queries. The queries
ran at a speed i considered accptable.
I then moved the tables in a second .mdb, put links to these in the first
.mdb and ran the queries (still in the first .mdb) . Contrary to my
expectations, the queries now run in 1/3 to 1/2 the time.
Can anyone this surprising phenomenon ?