I have observed that if u refresh path of / link tables from an external database (the backend) and if the backend is currently in use by some-one else on the network (LAN in my case) it takes a lot of time compared to when no one else is using it. Is there any way to get around this?
Speeding up linked tables
- Thread starter arvindn
- Start date
- Local time
- Today, 11:58
- Joined
- Feb 28, 2001
- Messages
- 30,554
Some users of more recent versions of Access have reported a slow-down such as you suggest. I have not ever noticed the problem myself, but my only production DB right now is in an older version of Access. I don't know that I have seen a fix for this problem in the articles in this forum, so I cannot advise you there, either. Nonetheless, there are reasons why Access DBs on networks are slower when someone has to share.
1. Basically, if you are on an NTFS disk, the permissions can take a while to evaluate, particularly if they are inherited permissions. Sharing the file means sharing the file security headers. AND you are also sharing the security headers of all the folders implied by the sharing. To counteract this problem, configure your system so you have a dedicated, top-level folder for your DB. This minimizes the side effects of permission inheritance. ('Top level' means 'only inherit from root folder'.)
2. How crowded is the folder in which your DB resides? Windows HATES crowded folders. It handles them but still hates them. Consider creating sub-folders for things not used directly by your DB. 'cause your .LDB file MUST be in the same folder as the .MDB file. How crowded is too crowded? If you need more than about 40 Kbytes for the folder alone, it is crowded.
3. Is the FE local to your disk or is it ALSO network-resident? Anything you can do on a local disk makes Access work faster/better.
4. Do the users have OpenExclusive permission for the DB? If so, you are adding extra file-system lock management overhead to determine who on the network has the DB open. And the more files that are statically open at once, the worse this gets.
5. Is there a lot of file activity (Opens, Closes, Folder Updates, Deletes, Creates, etc.) on the server hosting your BE DB? 'cause that 'churns' the buffers, file handles, and other resources needed for such action, thus incurring more 'garbage reclamation' overhead more often. If the server holding the BE DB is REALLY busy, your problem is resource waits. For that matter, how much memory is on that server and does the MS Resource Monitor (Performance Monitor) show anything operating at a very low level of free space or free resources?
These are all issues you can apply to help DB performance. Not all of them will be significant if the underlying problem wasn't that bad on your system.
1. Basically, if you are on an NTFS disk, the permissions can take a while to evaluate, particularly if they are inherited permissions. Sharing the file means sharing the file security headers. AND you are also sharing the security headers of all the folders implied by the sharing. To counteract this problem, configure your system so you have a dedicated, top-level folder for your DB. This minimizes the side effects of permission inheritance. ('Top level' means 'only inherit from root folder'.)
2. How crowded is the folder in which your DB resides? Windows HATES crowded folders. It handles them but still hates them. Consider creating sub-folders for things not used directly by your DB. 'cause your .LDB file MUST be in the same folder as the .MDB file. How crowded is too crowded? If you need more than about 40 Kbytes for the folder alone, it is crowded.
3. Is the FE local to your disk or is it ALSO network-resident? Anything you can do on a local disk makes Access work faster/better.
4. Do the users have OpenExclusive permission for the DB? If so, you are adding extra file-system lock management overhead to determine who on the network has the DB open. And the more files that are statically open at once, the worse this gets.
5. Is there a lot of file activity (Opens, Closes, Folder Updates, Deletes, Creates, etc.) on the server hosting your BE DB? 'cause that 'churns' the buffers, file handles, and other resources needed for such action, thus incurring more 'garbage reclamation' overhead more often. If the server holding the BE DB is REALLY busy, your problem is resource waits. For that matter, how much memory is on that server and does the MS Resource Monitor (Performance Monitor) show anything operating at a very low level of free space or free resources?
These are all issues you can apply to help DB performance. Not all of them will be significant if the underlying problem wasn't that bad on your system.
Thanks for replying.
No, i am not using a NTFS disk, the folder is not crowded, and there is not a lot of activity for sure.
The FE is on local disk.
I will try disabling open exclusive permission and see the result.
If anyone knows a walkaround , please let me know.
No, i am not using a NTFS disk, the folder is not crowded, and there is not a lot of activity for sure.
The FE is on local disk.
I will try disabling open exclusive permission and see the result.
If anyone knows a walkaround , please let me know.
Finally i got the correct solution after a long time and so i am posting it here for anyone having the same problem with refreshing links
http://support.microsoft.com/?id=150384
http://support.microsoft.com/?id=150384
