Linked Tables Performance

  • Thread starter Thread starter y770
  • Start date Start date
Y

y770

I ahve a database with a linked table. I have found that this link reduce the
performance of the database drastically.
I have seen the "http://www.granite.ab.ca/access/performancefaq.htm" page
but info was either not applicable or did not help much.
I have found that putting a line "set
db=OpenDatabase("LinkedDatabaseFileName") into Switchboard (the form that
opens on startup) onload action will help in this matter, but creates other
issues.

Any suggestions?
 
Rather than adding that to your Switchboard, what about the idea of creating
a startup form that you leave hidden (visible = false)? That way, you could
handle any of the initial processing you need, keep a connection open, and
still use your Switchboard.

--

Regards

Jeff Boyce
Microsoft Access MVP

Disclaimer: This author may have received products and services mentioned in
this post. Mention and/or description of a product or service herein does
not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.
 
Tried; Double trouble.
1. It did not helped to make forms faster (I do not understand why).
2. Cause other problems as has been mentioned previously.

Other problems include: When I am trying update (or add) records message
that I do not have necessary permissions appear (even thou I am running as
administrator and have all rights. I am not even modifying the linked table -
only the local one).
Also, as soon as I open any form, my database get locked by "another user"
and to modify (debug) code I need to close the database and re-start it
again. It is very cumbersome.

I am back to my 1st question: are there other way to speed up the
performance without “side effects†of running “set db=OpenDatabase()â€
command. I thought about copying that linked table into this DB (and it
removed the performance issue) but manually synchronizing the data in both
databases is too much of a trouble… There has to be a better way…

Thanks

y770
 
Back
Top