In a word: No. Or if it does, there's no real way to tune it such as in
Oracle.
About the best that you can do is index what is needed and not index what
isn't.
Also Access has a bad habit of creating indexes where the table names
include ID, key, code, or num. For example if you create a field called
Pers_id Access will create an index. If the Pers_id field is also the primary
key, Access will create two indexes for this one field. It will also index
Zipcode even though you don't want it to. This is controlled under Tools,
Options, Tables/Queries tab.
I once created, deleted, appended, and updated records on a large table with
an index. I timed a query that used the index. Next I deleted the index then
recreated it. There was an ever so slight performance increase.
