Helen,

> This occurs when you define your own index for a column that is also a primary
> or foreign key. IB doesn't stop you doing this but it results in NO index being
> used by the optimizer.

the optimizer is not THAT bad; let's say that it can be fooled sometimes
if duplicate indices exist. In my experience, it will more often pick up
one of the two than none.

Not that I am *by any means* suggesting to define duplicate indices! ;-)
Ciao
--
____
_/\/ando