Good, then the source of that error found. Still, it doesn't make the plan
reported by IBExpert any more sensible and you should correct your SQL like
I suggested to ascertain that correct results are returned (or check very
carefully that the returned results are as expected, containing the right
records, all the right records and nothing but the right records).

Set

At 13:26 20.06.2003 +0000, you wrote:

>Yes Set, he certanly is. I removed the field "nome_aluno"
>from the select and the error is gone. This field is the
>Varchar(80) and it's Charset and Collate as NONE.