> > Embedded SQL is talking about writing applications using gpre
> > and C/C++.
>
> This I believe has no effect on the fact that the example shows
> a cross-database query. If you're saying that the resulting
> executable performs the "joining" of the tables on the client
> then please confirm.

The example you refer to is...
EXEC SQL
DECLARE IDMATCH CURSOR FOR
SELECT TESTNO INTO :matchid FROM TEST.EMPLOYEE
WHERE (SELECT EMPNO FROM EMP.EMPLOYEE WHERE EMPNO = TESTNO);

In this case "TEST" (as in TEST.EMPLOYEE) and "EMP" (as in
EMP.EMPLOYEE) are not part of standard SQL. These are "handles" that
will have been declared earlier in your embedded SQL code - each
handle name will have been matched to a C variable (using the
application C header files). So the resulting application performs
the joining and not the server. How could it, the databases may even
be on different servers!

> I apologize for incorrect wording. By "third-party database" I
> meant "tables designed by someone else not me". It's Interbase,
> too. Does this leave a possible path other than replication?
> (Thanks for the link to the article.)

The link article is primarily about replication using Interbase - if
you were using something else then that would be your problem ;-)

Geoff Worboys
Telesis Computing