PREVIOUS TRANSMISSION [Historical Significance]
====================================================================
I am endeavoring to move information back and forth between an
ODBC database and SQL 6.5 ..., to date, with less than spectacular
results.

I have found a lot of information concerning the SQL 6.5 connection,
however, a lot less about what is involved when "talking" cross-
platform.  If anyone can help me with sources of information on this
subject, I would be very grateful.

Many thanks in advance,
Joseph Bailey
=====================================================================
END OF PREVIOUS TRANSMISSION

I obtained a note back from a recognized figure who writes articles
for many of the publications we read, however, asking him to elaborate
makes me feel as though I've crossed the "line" into irritation...
so I figured to post this message, ...and bother the newgroup instead.
Hey, I'm not proud of it either!

MY QUESTION WAS:
Is there a way (with RDO or some other fashion) to establish a
connection with an ODBC source, and another connection with
SQL Server, and then pass resultset information back and forth?
I don't think I've ever seen an example of this before, but I may
well be looking in the wrong places.

THE ANSWER WAS:
As for your other question. You can certainly open two different
connections to different databases from the same application. You
would then have to code exactly what data you wanted to pass back
and forth. There is no high level way of doing this. Basically you'd
have to create a resultset from one database and then send inserts or

updates to the other. It really depends what type of databases are
involved on how it would be done. SQL Server/Access would be different
from SQL Server/Oracle.

Does anyone have an example of what is being depicted here?  I'm going
"kookoo for Coco Puffs" here and would be keen on seeing how this is
done.  As always, just bill my account.

Please Respond: