And it probably uses it because you haven't got those two additional
indexes that I suggested (one natural for your first table I normally find
acceptable, but two is like multiplying them).

Set

At 13:47 02.07.2003 +0200, you wrote:

>Well, that's the plan the IB optimizer uses ... :-(
>
>At 01:55 PM 07/02/2003 +0200, you wrote:
>
> >What a dreadful plan, Tim!
> >
> >Assuming CODE is fairly selective, the following two indexes should help
> you:
> >
> >CREATE INDEX IDX_CLNT_SUB_CODE ON CLNT_SUB(CODE);
> >CREATE INDEX IDX_CLIENT ON CLIENT(CODE);
> >
> >If not selective, add the PK to the end of the index.