Yup, that's my bug. Here's a great deal more than you care to
know about the situation. The index in question RDB$INDEX_16 is
one of the indexes on the system tables, in this case on the
table RDB$FORMATS. It combines the RDB$RELATION_ID and the RDB$FORMAT
fields. In the old days, tables got new formats when someone added
or dropped a field. Being from the old days, I thought that index
ought to be unique - having a table with two different format 14's
is confusing.

Anyway, the unique constraint has been removed and the next build
will not have this problem.



Regards,

Ann
www.ibphoenix.com
We have answers.