mixing linked tables

[Gil]

hello i have a front end access application that has mixed linked
tables from 2 different sources.
some tables are linked to a MYODBC Driver and the other tables are
linked to an access database.
I know this sounds weird but it must be this way according to my
situation.

I am noticing that each time i run a query between the 2 linked tables
it takes very long for the new connection to load.

for example i have table A which is linked to the Myodbc source
and i have table B which is linked to the access database.

when i call a query from Table A it has to load for the first time, but
once it is loaded it can be called again instantly.
if i call a query from Table B after calling table A than i think table
A closes its connection automatically and opens a new connection for
Table B and table B goes through the same story. Slow first load, than
fast loads once it was loaded.

It seems like access can not keep two connections open at the same
time?

By the way... when working on the app locally its fast all of the time.
im only noticing this problem when working over the network.

[John Welch]

Re: mixing linked tables

Try keeping a persistent connection open to the data in both places. For
more info and ideas, check out Tony Toews' great tips at:

http://www.granite.ab.ca/access/performancefaq.htm

"Gil" <giloosh99@gmai l.com> wrote in message
news:1134826522 .204762.23830@g 49g2000cwa.goog legroups.com...[color=blue]
> hello i have a front end access application that has mixed linked
> tables from 2 different sources.
> some tables are linked to a MYODBC Driver and the other tables are
> linked to an access database.
> I know this sounds weird but it must be this way according to my
> situation.
>
> I am noticing that each time i run a query between the 2 linked tables
> it takes very long for the new connection to load.
>
> for example i have table A which is linked to the Myodbc source
> and i have table B which is linked to the access database.
>
> when i call a query from Table A it has to load for the first time, but
> once it is loaded it can be called again instantly.
> if i call a query from Table B after calling table A than i think table
> A closes its connection automatically and opens a new connection for
> Table B and table B goes through the same story. Slow first load, than
> fast loads once it was loaded.
>
> It seems like access can not keep two connections open at the same
> time?
>
> By the way... when working on the app locally its fast all of the time.
> im only noticing this problem when working over the network.
>[/color]