How to increase the response time by working with linked tables

[S. van Beek]

Dear reader,

How to increase the response in case of working with linked tables, program
in frond end mdb and tables in back end mdb.

For possible combinations and their response acceptance see next table:

Frond end mdb (Program)
Back end mdb (Tables) Respons

1. On local PC incl. tables in same mdb n.a.
Fast

2. On server including tables in same mdb n.a.
Acceptable

3. On local PC (linked tables) On
local PC Acceptable

4. On server (linked tables)
On server Not acceptable

5. On local PC (linked tables) On
server Not acceptable

I prefer the method as under number 5, program local and data on server, but
this delivers a very bad response of the application.

Is there any method to improve the response of the application by working
with linked tables?

Thanks for any help.

Kind regards,

Simon van Beek

[Albert D. Kallal]

Yes, if you keep a persistent connection from the FE to the BE, then
performance usually returns to un-split levels.

You can keep a persistent connection by either opening a form (any form)
that is connected to a table in the back end. You then can minimize this
form, and now for other forms etc, performance should be just fine. Another
alternative approach is to open up a table (any table in the BE) to a global
recordset, and keep that open. (so, the "key" concenpt here is to FORCE and
then KEEP the conneciton open).
Try the above, and then you can do things the corect way, (that is to
install the FE mde on each computer).

post back with your results (and, as mentieond, you should use a mde for the
FE).

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal