Kjell,

>> Rows that are returned when there's a WHERE clause, but not if there's
>> no WHERE clause doesn't make sense at all. What you could try, is to
>> locate the error. If you do a backup & restore, do you observe the
>> same behaviour on the restored copy? If not, that indicates that there
>> is an error in your database file. If the error occurs on the restored
>> copy as well, can you reproduce it using two separate tools, e.g.
>> FlameRobin and isql? If so, it looks as if Firebird is to blame,
>> though it's still uncertain whether it is a general error or something
>> related to a particular character set or collation. What's the DDL of
>> Namn, ECO_ID and Kod (I don't know enough to be of any more help, but
>> find it more understandable if things like this occur if e.g. Namn is
>> defined as a BLOB or a huge (VAR)CHAR or if you use a character
>> set/collation that you've defined yourself)?
>>
>
> Yes, I guess I'll have to do some tests like that, now that I can
> conclude that noone seems to be able to find an error in my SQL or
> something. The DB is a bit large, so it's going to take a while, but I
> suppose it's worth the effort to locate the error.

*Could* be related to:

http://tracker.firebirdsql.org/browse/CORE-2277
or
http://tracker.firebirdsql.org/browse/CORE-2164


Regards,
Thomas