Submitted by: @pcisar

after misspelling table in 'type of column' declaration
error message begins with 'column does not exists',
thus developers start looking for problems in wrong place (columns),
and it may take a while to spot real error (table), e.g.:

set term ^ ;
create or alter procedure test_err
as
declare variable var type of column tbl.fld;
begin
select fld from tbl into :var;
end
^
set term ; ^
commit;

/*column FLD does not exist in table/view TBL*/

would it be possible to improve error messages
and make it work like in 'select' statements (table has priority over columns):

select fld from tbl;

/*-Table unknown
-TBL*/

select fld from rdb$database;

/*-Column unknown
-FLD*/