Many of my clients have "upgraded" to Access 2000 in the past year or so. Most have suffered through poor performance and just accepted it.
I have a few applications, however, where the performance is so poor that they border on "unuseable". These are sytems that have been in place for 3 or 4 years, running quite successfully under Access 97, but now are so slow that they must be modified or abandoned in favor of some other solution. I have had to "add" hourglasses and "Wait..calculating" prompts to assure the users that the app is actually working, when for years this was not necessary.
By way of example, I have a form, based on a query that does some calculations, which loads and refreshes in 4 seconds in Access 97. It takes (varies) from 9 to 20 seconds in A2K. This is using all local tables on the same machine. The ONLY difference is that the mdb is converted to A2k.
Can anyone offer any tips for speeding up A2k SPECIFICALLY, particularly in Networked environments with linked tables .. is there some different Jet that can be used? some special query optimizations? should I use code modules instead of code behind the forms? create relations or just JOIN in queries? more tables related to each other or fewer tables with more fields? yada yada yada ..
I have of course compacted, indexed, etc. All hardware has PLENTY of memory and in most cases are MUCH faster machines than they used to have. The amount of data is NOT a cause, we have archived and pared down files beyond the client's desires.
I would welcome any tips that relate specifically to Access2k (not defrag, empty recycle bin, etc. please) and any insights into XP (is it faster? faster than 97?).
Thanks in advance.
Holding back some points for multiple awards ..:)
Start Free Trial
