Dear experts -
I am now fine-tuning an application that is basically working well.
We have indexes defined in all tables on key fields.
However, we have not defined ANY composite indexes (if I'm using the term correctly - I mean an index based on more than one field).
The real workhorse of the system is a Project table, that has a number of child tables, most notably one called Project_Parts. Do we, for example, want to have a project_ID + Part_ID composite index on the parts table? Would this be standard, or not?
I used to work a lot in Foxpro, and indexes like this made a HUGE difference.
a related question - nowhere in our system do i 'tell' the code to use a given index; a programmer told me once that Access takes care of all this and 'knows' which indexes to use.
Can someone give me a bit of orientation on the above?