At 11:51 AM 16/04/2005 +0200, you wrote:

http://www.ibobjects.com/ibo_fb2_issues.html

regards,
Helen

> > be aware, IBO system table queries will fail with Firebird 2.0. Firebird
> > 2.0 got more restrictive with using table names where a table alias
> > has been already defined. For example:
> >
> > One of IBObjects system table query is:
> >
> > SELECT RDB$INDEX_SEGMENTS.RDB$FIELD_NAME
> > , RDB$INDICES.RDB$RELATION_NAME
> > FROM RDB$RELATION_CONSTRAINTS C
> > , RDB$INDICES I
> > , RDB$INDEX_SEGMENTS S
> > WHERE RDB$CONSTRAINT_TYPE = 'FOREIGN KEY'
> > AND C.RDB$RELATION_NAME = I.RDB$RELATION_NAME
> > AND C.RDB$INDEX_NAME = I.RDB$INDEX_NAME
> > AND I.RDB$INDEX_NAME = S.RDB$INDEX_NAME
> > ORDER BY 1 ASC
> > , S.RDB$FIELD_POSITION ASC
> >
> > The query will fail with the following error message:
> >
> > Dynamic SQL Error SQL error code = -206 Column unknown
> > RDB$INDEX_SEGMENTS.RDB$FIELD_NAME At line 1, column 27.
> >
> >
> > The query will work, if using table aliases in the SELECT field list.
> > For example:
> >
> > SELECT S.RDB$FIELD_NAME
> > , I.RDB$RELATION_NAME
> > FROM RDB$RELATION_CONSTRAINTS C
> > , RDB$INDICES I
> > , RDB$INDEX_SEGMENTS S
> > WHERE RDB$CONSTRAINT_TYPE = 'FOREIGN KEY'
> > AND C.RDB$RELATION_NAME = I.RDB$RELATION_NAME
> > AND C.RDB$INDEX_NAME = I.RDB$INDEX_NAME
> > AND I.RDB$INDEX_NAME = S.RDB$INDEX_NAME
> > ORDER BY 1 ASC
> > , S.RDB$FIELD_POSITION ASC
>
>Any news on that?
>
>
>Thanks,
>Thomas
>
>
>
>___________________________________________________________________________
>IB Objects - direct, complete, custom connectivity to Firebird or InterBase
> without the need for BDE, ODBC or any other layer.
>___________________________________________________________________________
>http://www.ibobjects.com - your IBO community resource for Tech Info papers,
>keyword-searchable FAQ, community code contributions and more !
>Yahoo! Groups Links
>
>
>
>