Query in front end takes a long time (7 secs) to display in designmode.

[Chrisso]

Hi All

I have a MS Access database used over the network so I have split the
DB into a front end and a back end.

When I open a query in design mode in the front end on my desktop it
takes a very long time (7 secs) to display. I am surprised by this as
the query is in the front end and should display in design mode
immediately.

What could be taking the time? Is Access checking the query against
the tables in the back end?

Is there anything I can do to speed this up as this will really slow
down my developement.

Chrisso

 

[Albert D. Kallal]

Is there anything I can do to speed this up as this will really slow
down my developement.

Beofre you open up the query in desing mode, go to the table view, and open
up ANY table that is a linked table tot he back end. Now, miniize this
table, and then now go to the query window, and try desing mode for your
query......

And, do post back here for everyone else to learn how this fixed this for
you.....

Note that it does not matter WHICH table you opened and minimized in the
above..(it does not eve have to the same one the query is based on)....

So, yes, ms-access is checking fields, default values, and many other things
from that back end table....

By the way, if your performance improves, you want to use this "trick" when
your application is running to also speed things up. This is called a
persistent connection. It means that you want to your application to keep a
connection open to the back end at all times....

So, in your startup code...do open some table, or ensure that a form is
ALWAYS opened to some table in the back end...else you will experience the
same above delays not only during development, but when in fact users are
running your application....

 

[Chrisso]

Beofre you open up the query in desing mode, go to the table view, and open
up ANY table that is a linked table tot he back end. Now, miniize this
table, and then now go to the query window, and try desing mode for your
query......

And, do post back here for everyone else to learn how this fixed this for
you.....

Note that it does not matter WHICH table you opened and minimized in the
above..(it does not eve have to the same one the query is based on)....

So, yes, ms-access is checking fields, default values, and many other things
from that back end table....

By the way, if your performance improves, you want to use this "trick" when
your application is running to also speed things up. This is called a
persistent connection. It means that you want to your application to keepa
connection open to the back end at all times....

So, in your startup code...do open some table, or ensure that a form is
ALWAYS opened to some table in the back end...else you will experience the
same above delays not only during development, but when in fact users are
running your application....

Thanks Albert - that did the trick nicely. I have also followed your
suggestion to incorporate this into my system during run time.

Thanks for your help,
Chrisso