Hi Andrew,

> Anyway, try adding a dummy WHERE clause to your view to force the
> engine to engage available indexes, e.g. use the index for NUMMER
> thusly:
>
> WHERE NUMMER = NUMMER

I think the dumb/broken optimizer is not my problem.
The problem is that even if I tell the optimizer which plan to use
it refuses to use the index
("index RDB$PRIMARY16 cannot be used in the specified plan")
which is correctly used by the select statement which joins the two
tables.

Weird, isn't it? Seems this is one for the IB/FB gurus.
BTW, I hope Helen will switch on her computer before she
furnishes the rest of her new home :-)


Christian


PS: Anyway, I tried to use the dummy WHERE clause, but the result
was still the same.