So run the code in the above mentioned Q261000 article in the Access 97 backend. Note that if you have Name Auto Correct on this will change the Subdatasheet property back to [Auto] for each table to which you make a change. There are many web pages on this topic both Access specific and general relational database systems so I'm not going to get into the details here..
The best choice to reduce the impact of this change is work on all the database files located on the local system and not on the server.
- New format of Access MDB - Place backend MDB on the root of the network share rather than several folders down - Shorten the name of the backend MDB - Miscellaneous Performance Suggestions - Virus scanning - System utilities - Outlook 97 Journaling - Queries up to five times slower if user defined functions and Jet 4.0 SP4 or 5 - Use of DSUM, DCOUNT, etc after splitting - Disable SMB Signing - Set Can Grow and Can Shrink on forms section properties to No - Access 2007 design view performance on Vista vs XP - Windows Vista, ODBC and SQL Server 2005 - Playing music severely degrades network transfer performance in Windows Vista before the first line of code is run then it likely needs a decompile.
Any of the following tips can also apply in this situation.
Also make sure you have the fastest available reasonably priced (don't go spending lots of money on SCSI if you don't need to) hard drive controller systems and hard drives. I'm quite happy with the performance of my tower systems IDE 100 controller and hard drives. For more information see ACC2000: Saving Objects in DB Slower Than in Earlier Versions - 246306 The problem is likely related to server security as each directory you navigate must be checked against the domain security system.
This may be particularly acute in combo boxes and subreports when using a FE/BE system as I've noticed these appear to be poorly optimized.