468,107 Members | 1,308 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

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

Performance by working with linked tables

Dear reader,

By working with a frond-end and back-end databases with the use of linked
tables the performance, if both mdb's are on a local drive is reasonable.

But in case the backend is located on a network drive the performance is
decreasing drastically.

And in particularly the comboboxes are working very slowly.

By activating a combobox the message pops up "Not responding" and after a
few seconds it disappear and the combobox opens.

Is there any solution to solve this inconvenience behavior of working with
linked tables on a network drive?

Thanks for any help.

Kind regards,

Simon van Beek



Nov 13 '05 #1
2 1552
On Fri, 28 Oct 2005 09:49:01 +0200, "S. van Beek" <S.******@HCCnet.nl> wrote:
Dear reader,

By working with a frond-end and back-end databases with the use of linked
tables the performance, if both mdb's are on a local drive is reasonable.

But in case the backend is located on a network drive the performance is
decreasing drastically.

And in particularly the comboboxes are working very slowly.

By activating a combobox the message pops up "Not responding" and after a
few seconds it disappear and the combobox opens.

Is there any solution to solve this inconvenience behavior of working with
linked tables on a network drive?

Thanks for any help.

Kind regards,

Simon van Beek


A network is slower than a hard drive, so accessing data over a network is
slower than accessing data from the hard drive. If a combo box is too slow,
it is selectig too much data. You should modify the application design, so
one combo box will never be used to select that many rows at once.
Nov 13 '05 #2
"S. van Beek" <S.******@HCCnet.nl> wrote in message
news:43*********************@reader1.nntp.hccnet.n l...
Dear reader,

By working with a frond-end and back-end databases with the use of linked
tables the performance, if both mdb's are on a local drive is reasonable.

But in case the backend is located on a network drive the performance is
decreasing drastically.

And in particularly the comboboxes are working very slowly.

By activating a combobox the message pops up "Not responding" and after a
few seconds it disappear and the combobox opens.

Is there any solution to solve this inconvenience behavior of working with
linked tables on a network drive?

Thanks for any help.

Kind regards,

Simon van Beek


Try deleting all the linked tables completely and then re-creating them.
Although simply refreshing the links should work in theory, in practice I
have had more than one situation where network performance was still very
poor after refreshing, but was dramatically improved by the above technique.
I would also recommend this after any backend table changes
Let us know if it helps or not.
Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by robert | last post: by
5 posts views Thread by Scott | last post: by
1 post views Thread by Simon | last post: by
4 posts views Thread by Jim Devenish | last post: by
4 posts views Thread by Jana | last post: by
1 post views Thread by Solo | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.