Guido,

> > I doubt that the replicator is using a union to do it's work. There's no
> > need. It's more likely something in your database design which is causing
> > ambiguity
>
> It's not my DB, it's in the configuration-db from IBReplicator. I have no
> influence, what is done there.
> Is this bug closed in FB 1.0 ? Do you know anything about that ?

IBReplicator needs a fix if it intends to support Firebird, which I'm
unsure of. You should ask the producer about that.
There isn't any bug left in Firebird to fix WRT ambiguous field names,
except perhaps the cases when perfectly legal and unambiguous queries
like

select CUSTNO
from CUSTOMER join ORDER on CUSTOMER.CUSTNO = ORDER.CUSTNO)

get rejected. Looking at the error message you have posted, I suspect
that the two tables are joined on the DBNO field, so the query isn't
really ambiguous except for Firebird. I bet it would be extremely
difficult to make it smarter than that, otherwise Claudio would have
done it when he introduced the original fix.

I personally prefer the current behaviour, though not perfect, over the
old behaviour which let really ambiguous queries in.

Oh, and don't worry, your database design isn't causing any ambiguity.
:-)

Ciao
--
____
_/\/ando