dynamically linked tables adn slow performance

[Guest]

I have an application .mdb that has links to tables in another .mdb file.
When the tables .mdb is on a server and the appl is on a workstation in the
same network, I want to dynamically link the tables when the appl first
starts. But when I do this it takes a VERY long time for the the tables to
get linked. When I take away the dynamic liknking and just leave the 'manual'
links it starts up quickly. Also, the dynamic links are not slow when the
appl .mdb and tables .mdb are on the same machine. There are other
applications that the user is running from the one workstation where the
application is being run from the server, and without the dynamic links
everything runs fine on the server, so the server and network don't seem to
be the problem. Any idea why the dynamic linking would be so slow when being
done remotely, but not when done locally? Are there some parameters I don't
know about that affect performance in this situation? Any help is
appreciated! I eventually need to be able to do dynamic linking because the
drive name won't always be the same depending on where the application is
running.

 

[Allen Browne]

Jim, how about testing the links (try OpenRecordset on a linked table, with
error handling), and bypass the relinking if that works?

It also helps to OpenRecordset() on the back end while you are relinking the
tables. Although you don't actually use this variable, just holding the file
open until the relinking is done make a significant difference.

For other suggestions, see the Access performance FAQ:
http://www.granite.ab.ca/access/performancefaq.htm

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

message
news:[email protected]...

 

[Guest]

For some stupid reason I hadn't thought of that. Thanks. And thanks for the
link to the FAQs.