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

Alan
-----Original Message-----
From: guido.klapperich@... [mailto:guido.klapperich@...]
Sent: Saturday, 14 September 2002 9:52
To: ib-support@yahoogroups.com
Subject: Re: [ib-support] Ambiguous field name

> Guido,
> are you trying to select fields from these two tables where the same
> fieldname exists?
> are you using aliases?

That's a good question :-) The problem is, that the Replication-Manager
from
the product IBReplicator produces this error and I don't know, what it is
internally doing. BTW, only with FB, with IB all works fine.
I have seen in the Closed Bugs of FB the following:
Unions that work with earlier versions and use same tables usually get
this
errors for example (employee.gdb):
SELECT J.PROJ_ID,J.PROJ_NAME,1
FROM PROJECT J
UNION
SELECT J.PROJ_ID,J.PROJ_NAME,2
FROM PROJECT J

Dynamic SQL Error
SQL error code = -204
Ambiguous field name between table/view PROJECT and
table/view PROJECT PROJ_ID.
In fact, there is not ambiguity here because each select is independent
and
has his aliases or tables, traditionally because this ORDER BY clause in
UNION
must use numbers instead of field names.

But there is also written, that this bug is fixed in v1.0


Guido


Yahoo! Groups Sponsor
ADVERTISEMENT




To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



[Non-text portions of this message have been removed]