We all want speed and faster performance in Microsoft Access. As tables get larger, secondary indexes can help speedup queries, searches, and links between tables.
Leisure Jacket Leisure Winter Republic Leisure Banana Winter Jacket Republic Banana Winter By default, Microsoft Access has a setting that automatically adds secondary indexes on fields based on their name. Unfortunately, this can create additional problems.
By default, Access automatically adds a secondary index to fields that begin or end with these names:
Jacket Republic Winter Republic Winter Leisure Winter Banana Banana Leisure Jacket Leisure These are set in the options AutoIndex on Import/Create separated by semicolons:
21 Forever Boutique Cocktail Winter Dress BHwWx6q
For Microsoft Access 2010 and later, this option is under File, Options, Object Designers:
Jacket Winter Republic Leisure Banana Leisure Winter Jacket Banana Leisure Winter Republic For Microsoft Access 2007, this option is under the Office button, Access Options, Object Designers:
For Microsoft Access versions before Access 2007, the setting is on the Tables/Queries tab under the Access Tools/Options menu:
Adding too many indexes to a table and duplicating indexes on the same field can hurt performance and increase your database size.
When you import a table with these settings, the indexes are added to your new table automatically. That may be fine for a brand new table, but if you are importing a table to replace an existing table (from a backup) or creating a new database by importing all the tables from an existing database, a whole set of new secondary indexes may be added unnecessarily -- essentially undoing the work you may have done to determine which fields shouldn't have indexes.
If you understand when to add secondary indexes on your tables, you should set the AutoIndex on Import/Create option to nothing. This lets you control where and when indexes are added, and eliminates it from happening by chance:
If you have our Total Access Analyzer program, this setting is one of the ~300 issues detected when your database is documented. Learn more about how Total Access Analyzer can help you create better Microsoft Access applications.