|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
October 6th, 2009, 08:41 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
Link updates are very slow
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? 
|
|
#2
October 7th, 2009, 08:11 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Link updates are very slow
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. -- Milton Purdy ACCESS State of Arkansas "TADropik" wrote: 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?
|
|
#3
October 8th, 2009, 02:28 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Link updates are very slow
TADropik wrote:
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? 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 -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ Granite Fleet Manager http://www.granitefleet.com/
|
|
#4
October 9th, 2009, 05:29 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Link updates are very slow
Thank you.
This along with the UNC paths made a HUGE difference in the speed. "Tony Toews [MVP]" wrote: TADropik wrote: 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? 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 -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ Granite Fleet Manager http://www.granitefleet.com/
|
|
#5
October 9th, 2009, 09:26 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Link updates are very slow
TADropik wrote:
This along with the UNC paths made a HUGE difference in the speed. It would be interesting in knowing if UNC paths by themselves make any difference. Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ Granite Fleet Manager http://www.granitefleet.com/
|
|
#6
October 9th, 2009, 11:18 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Link updates are very slow
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. "Tony Toews [MVP]" wrote: TADropik wrote: This along with the UNC paths made a HUGE difference in the speed. It would be interesting in knowing if UNC paths by themselves make any difference. Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ Granite Fleet Manager http://www.granitefleet.com/
|
|
#7
October 10th, 2009, 03:18 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Link updates are very slow
TADropik wrote:
Great question Tony. I did some testing with this. The UNC paths alone were actually slower than using a mapped drive letter. Now isn't that interesting It was setting the database variable that increased the speed. 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. Generally UNC paths are better but not always. Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ Granite Fleet Manager http://www.granitefleet.com/
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
