Link updates are very slow

  • Thread starter Thread starter TADropik
  • Start date Start date
T

TADropik

I have a .mdb on a network drive, L:\Data\data.mdb.
This database contains nothing but tables. About 100 of them.

I have a .mdb on a local computer C:\Data\data.mdb.
This database contains nothing but tables. About 100 of them.

I have a .mdb on a local computer C:\Data\client1.mdb.
This database links to all the tables in the .mdb C:\Data\data.mdb on the
same local.

I have another .mdb on a different local computer C:\Dta\Client2.mdb
This database links to all the tables in the .mdb L:\Data\data.mdb on the
Network.
This database has automated functions built in that update the data
periodically.

The problem I have is...

When I want to change the table links from C:\Data\Client1.mdb on the first
local to the tables on the Network, it takes forever for the link update to
finish.

If I close down C:\Data\Client2.mdb the update link process on
C:\Data\Client1.mdb happens exrtremely fast.

Anything I can do to speed up the link update from C:\Data\Client1.mdb to
L:\Data\Data.mdb while c:\Data\Client2.mdb is still up and running?
 
On the network drive, be sure and use UNC paths. It will be much faster. Use
paths such as:
\\server\directory\filename
Google unc path names or check help.
 
TADropik said:
If I close down C:\Data\Client2.mdb the update link process on
C:\Data\Client1.mdb happens exrtremely fast.

Anything I can do to speed up the link update from C:\Data\Client1.mdb to
L:\Data\Data.mdb while c:\Data\Client2.mdb is still up and running?
Click to expand...

You can open a database variable to L:\Data\Data.mdb before doing the
relinking. This will keep the LDB file open and the linking should go
about 10 times as fast.

Tony
 
TADropik said:
This along with the UNC paths made a HUGE difference in the speed.
Click to expand...

It would be interesting in knowing if UNC paths by themselves make any
difference.

Tony
 
Great question Tony.

I did some testing with this.

The UNC paths alone were actually slower than using a mapped drive letter.

It was setting the database variable that increased the speed.

I like the benefits of the UNC paths though. Some of my clients us VPN to
connect to the network and don't always get their network drives connected
accordingly.

Thanks again for your help.
 
TADropik said:
Great question Tony.

I did some testing with this.

The UNC paths alone were actually slower than using a mapped drive letter.
Click to expand...

Now isn't that interesting
It was setting the database variable that increased the speed.
Click to expand...

That's what I thought.
I like the benefits of the UNC paths though. Some of my clients us VPN to
connect to the network and don't always get their network drives connected
accordingly.
Click to expand...

Generally UNC paths are better but not always.

Tony
 
Back
Top