Dan
I found the hard way that you cannot connect to a table in another
database
that has the same column names as the db you are connecting from -- I
think
this mainly applies to columns with the same name but different
datatypes -
I have seen this for sure. I also think this applies to the column names
themselves.. I don't know why it was set up like this, but one other way
to handle this is to
DISCONNECT
CONNECT --- to another dummy database and SCONNECT / SATTACH in it.
Dump contents of SAttach table into another with column names that are
not in yours... --- BEAT THAT..
Then DISCONNECT
CONNECT --- to your db
SCONNECT to the dummy db
SAttach the new table and your IN....
Hope this helps
Jim Limburg
Dan Weissmann wrote:
>
> Greetings all. I'm having my first experience of trying to use SATTACH and
> SCONNECT. The table in the foreign source (a Sybase table) appears to
> connect fine, but RBase shows the table as empty (no rows). I also receive
> an error message when connecting which indicates that a few column names are
> illegal in Rbase. Could this be why RBase sees the table as empty?
>
> Thanks,
>
> Dan
