RE: SCONNECT and Illegal Column Names

[Phil Nolette \(NCS Group, Inc.\)]

Ben,
I just finished with this problem.  I had two ODBC connections to SQLSERVER
databases.  One of the databases was designed and built by some Microsoft
Consultants and I believe that they got paid by the characters.  The names
totally violated ANSI SQL standards.  Needing the data I got in touch with
the DBA and had him create a view with compliant names.  There is a
perceived drawback to this as I believe the performance was reduced.  If I
would have had an alias capability, I could have taken care of this by my
own.  The alias capability has to be at the very front of the ODBC
connection start.

Phil Nolette
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Ben Johansen
Sent: Wednesday, August 22, 2001 1:28 PM
To: [EMAIL PROTECTED]
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
>
>
>
>