If you create a relation between two tables and enforce referential
integrity, Access creates a hidden index on the foreign key field. There is
therefore no need to index your foreign key field yourself.
That remains true for a multi-field key such as the OrderDetails in
Northwind, where there are two relations going to 2 different tables (Orders
and Products), because that involves an index on each one.
However if you have a multi-field relation (a relationship to another table
based on 2 or more fields), Access will give you a multi-field index.
Rushmore can then use the first field in the index as if it were indexed
itself, but you may want to index the 2nd and subsequent fields yourself.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Kostas" <no*****@noemail.net> wrote in message
news:10*************@corp.supernews.com...
Hi all,
I was wondering what's happening in a typical junction table where the
primary key is the combination of two foreign keys from other tables.
I suppose Access automatically creates a concatenated index on the two
attributes that comprise the primary key.
Should I be indexing each attribute separately as well?