468,134 Members | 1,276 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,134 developers. It's quick & easy.

Working with linked tables on a network server

Dear reader,

To work with linked tables is a professional method of working with a frond
end and back end mdb.

Working with linked tables on a local pc gives an acceptable performance but
in case you start working with linked tables on a server (network) the
performance will be drastically reduce.

After moving the tables into the frond end database the performance is
slightly increasing.

Is there any possibility to increase the performance for an application
working with linked tables on a network server?

Tanks for any help.

Kind regards,

Simon van Beek
Nov 13 '05 #1
3 2079
No, it's not possible. Access will always be running on the workstation, not
the server, so placing the links on the server buys you nothing (except
increasing the complication)

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

"S. van Beek" <S.******@HCCnet.nl> wrote in message
news:42*********************@reader1.nntp.hccnet.n l...
Dear reader,

To work with linked tables is a professional method of working with a
frond
end and back end mdb.

Working with linked tables on a local pc gives an acceptable performance
but
in case you start working with linked tables on a server (network) the
performance will be drastically reduce.

After moving the tables into the frond end database the performance is
slightly increasing.

Is there any possibility to increase the performance for an application
working with linked tables on a network server?

Tanks for any help.

Kind regards,

Simon van Beek

Nov 13 '05 #2
S. van Beek wrote:
To work with linked tables is a professional method of working with a frond
end and back end mdb.

Working with linked tables on a local pc gives an acceptable performance but
in case you start working with linked tables on a server (network) the
performance will be drastically reduce.

After moving the tables into the frond end database the performance is
slightly increasing.

Is there any possibility to increase the performance for an application
working with linked tables on a network server?


I have never found linked tables on a network server to slow down
anything noticeably. I assume you have a poor network and/or an
inefficient application, and/or your expectations are way beyond
Access/Jet capabilities.

As you say, "slightly increasing", I would guess inefficient application
or unreasonable expectations.

There may be other possible reasons, and others may post them.

--
--
Lyle
Nov 13 '05 #3
Often, when you split a database,a nd try it you find that things seem to
run slow.

If you keep a persistent connection open at all times, then I find the
performance is returned to as before.

A persistent connection means that the Front end MUST KEEP a back end table
open AT ALL TIMES!!!

So, in your startup code, have it open a table to the back end, or even a
small form attached to some table in the back end (and then you minimize
this form..and also can make it visible = false.

If you do the above, then you will find that the split performance on the
network will be restored to normal performance.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal
Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by infopimp | last post: by
1 post views Thread by Simon | last post: by
10 posts views Thread by Jim Devenish | last post: by
1 post views Thread by BillCo | last post: by
reply views Thread by Nathan | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.