Unfortunately I can't do any one of those things as it's a third party app.
If I had any say in it's development, the engine it used would start with
the letter 'O'.
Since I'm having to pull in an identical table, and since the Sybase table
structure is subject to weekly changes as the product matures, I can't
really have a set table on the Rbase side. What I've had to end up doing was
pull the data into Excel, save it as a DBF file, attach it to RBase while
renaming the conflicting columns (imagine, they actually have a column
called RDate!), and project it to a new RBase table. I'm no longer working
with live data, but at least I can read it.
Dan
----- Original Message -----
From: "Ben Johansen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 22, 2001 12:27 PM
Subject: RE: SCONNECT and Illegal Column Names
DBase was basically a header section to define the data in each comma
seperated position.
therefore R:Base could ignore the name and just use the position in the
record. This goes away when you have the SATTACH because you have to deal
with rules of the SCONNECT'ED database.
I brought this issue up many times to the people of Microrim years ago.
I asked for aliasing the column name coming in. I guess this will have to be
up to RBTI to determine the need for this functionality.
One more issue (might have been fixed in the newer version of RBase 6.5) is
the limitation
of column name length limited to 18 characters and no spaces.
you've got few options.
1. change the conflicting columns in R:Base
2. change the conflicting columns in Sybase
3. create a view on the sybase side that aliases the column names
4. Create an intermediary process to get the data in through a gateway
process
Ben Johansen - www.pcforge.com
list commands: www.pcforge.com/WiTangoTalk.htm
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Dan Weissmann
Sent: Wednesday, August 22, 2001 9:25 AM
To: [EMAIL PROTECTED]
Subject: Re: SCONNECT and Illegal Column Names
Ah, then how do you change the column names when attaching so you can read
the data? I've had RBase prompt me for this when similar problems occurred
in attaching a dbf with the ATTACH command. With SATTACH I just get a
warning.
Dan
----- Original Message -----
From: "Ben Johansen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 22, 2001 10:45 AM
Subject: RE: SCONNECT and Illegal Column Names
> Yes,
>
> Try "SET ANSI OFF"
>
> The other issue is a column name in Sybase is the same name as a column in
> RBase and different data types or length. One of them has to change...
>
>
> Ben Johansen - www.pcforge.com
> list commands: www.pcforge.com/WiTangoTalk.htm
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Dan Weissmann
> Sent: Wednesday, August 22, 2001 7:28 AM
> To: RBase List Server
> Subject: SCONNECT and Illegal Column Names
>
>
> 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
>
>
>
>
