FreeTDS Development Group

[Brian Bruns <camber AT umcc.ais.org>]

Properties 32 and 40 are CS_APPNAME and CS_LOC_PROP respectively. 

For CS_APPNAME the following can be added to ct_con_props (in the CS_GET
section)

             case CS_APPNAME:
                  tds_set_app(con->tds_login,(char *)buffer);
                  break;
 
I'll check this in sometime tonight...for CS_LOC_PROP things are a bit
more difficult, since there is no locales support in FreeTDS. (Not to be a
total American, but its really not an itch I have need to scratch). In any
event neither of these will affect the proper functioning of FreeTDS under
SQSH.
 
Feel free to implement locales if you require them ;)

Brian

P.S. If you have reproducable problems with anything else, let me know.  I
can usually get a fix out pretty quick if it's minor. Just send the table
layout and the query.

On Tue, 1 Jun 1999, T.B. wrote:

> Hey all,
> 
> I am not certain if this has been dealt with here.. I searched the list a 
> bit but could not find an explicit description of this situation, so I 
> thought I would relate my travails with this setup.
> 
> On an RedHat 5.2 System, using gcc 2.7.2.3 I was able to successfully 
> compile freetds and sqsh, and connect to an MSSQL7.0 server using sqsh from 
> a Linux server.
> 
> The fun bit was that MSSQL7.0 is NOT compatible with TDS version above 4.2 
> (or so we finally wheedled out of Microsoft tech support). That is to say, 
> it is -intentionally- incompatible with TDS ver above 4.2. "We don't 
> support TDS versions above 4.2 in MSSQL 7.0". When we finally discovered 
> that fun fact, I abandoned the sybase libs, got freetds and compiled it 
> using tdsver=4.2 and installed it normally.
> 
> Then, I untarred sqsh, removed configure and executed 'autoconf', then 
> configured and made the binary. I still get two errors when the command 
> prompt is coming up, however it seems to work nicely. For the curious, 
> those errors are:
> 
> Unknown property 32
> Unknown property 40
> 
> -Timothy
> 
> 
>