Hello Jason,

fixing IB_Schema.pas regarding table name/alias usage is only half of
the story for Firebird 2.0 support. I've encountered another issue,
namely full qualified table names in properties like MasterLinks, ...

Have a look in IBF_Browse.pas, for instance the query "qrConstraintInf".

This query has the following MasterLinks property:

RDB$RELATION_CONSTRAINTS.RDB$RELATION_NAME=RDB$RELATIONS.RDB$RELATION_NAME

Opening the query (double-click a TIB_Connection component and select
Browse Database) will fail. The following MasterLinks entry will fix
that problem:

RC.RDB$RELATION_NAME=RDB$RELATIONS.RDB$RELATION_NAME


With Firebird 2.0, one needs to be extremely careful using full qualifed
table/field pair values, when there is a table alias used in the SQL
statement.


--
HTH,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com