FreeTDS Development Group

["Ian Harding" <ianh AT tpchd.org>]

When I connect via SQL Anywhere isql I get the errors, and when I connect via 
Microsoft SQL Server Query Analyzer (isqlw) which uses TDS via the Oopen 
Server Gateway product, I get the errors.

This leaves freetds and nsfreetds as culprits.

The nsfreetds/freetds combo works great against MSSQL Server 7.0; i.e. it 
returns error messages. (using TDS7.0, of course.)

That narrows it down to the fact that I am using TDS5.0 with freetds and 
nsfreetds.

I have logging turned on, if anyone is interested in seeing the last few 
lines...


Sending packet @ 2001-07-25 16:08:30
0000  0f 01 01 32 00 00 00 00 76 65 72 74 28 64 61 74   |...2....vert(dat|
0010  65 74 69 6d 65 2c 20 6e 75 6c 6c 29 20 64 61 74   |etime, null) dat|
0020  65 74 69 6d 65 5f 6e 75 6c 6c 2c 0d 0a 20 20 20   |etime_null,..   |
0030  20 20 20 20 20 63 6f 6e 76 65 72 74 28 69 6e 74   |     convert(int|
0040  65 67 65 72 2c 20 6e 75 6c 6c 29 20 69 6e 74 65   |eger, null) inte|
0050  67 65 72 5f 6e 75 6c 6c 2c 0d 0a 20 20 20 20 20   |ger_null,..     |
0060  20 20 20 63 6f 6e 76 65 72 74 28 72 65 61 6c 2c   |   convert(real,|
0070  20 6e 75 6c 6c 29 20 72 65 61 6c 5f 6e 75 6c 6c   | null) real_null|
0080  2c 0d 0a 20 20 20 20 20 20 20 20 63 6f 6e 76 65   |,..        conve|
0090  72 74 28 6e 75 6d 65 72 69 63 2c 20 6e 75 6c 6c   |rt(numeric, null|
00a0  29 20 6e 75 6d 65 72 69 63 5f 6e 75 6c 6c 2c 0d   |) numeric_null,.|
00b0  0a 20 20 20 20 20 20 20 20 63 6f 6e 76 65 72 74   |.        convert|
00c0  28 6d 6f 6e 65 79 2c 20 6e 75 6c 6c 29 20 6d 6f   |(money, null) mo|
00d0  6e 65 79 5f 6e 75 6c 6c 2c 0d 0a 20 20 20 20 20   |ney_null,..     |
00e0  20 20 20 63 6f 6e 76 65 72 74 28 76 61 72 63 68   |   convert(varch|
00f0  61 72 28 31 30 29 2c 20 6e 75 6c 6c 29 20 76 61   |ar(10), null) va|
0100  72 63 68 61 72 5f 6e 75 6c 6c 2c 0d 0a 20 20 20   |rchar_null,..   |
0110  20 20 20 20 20 63 6f 6e 76 65 72 74 28 74 65 78   |     convert(tex|
0120  74 2c 20 6e 75 6c 6c 29 20 74 65 78 74 5f 6e 75   |t, null) text_nu|
0130  6c 6c                                             |ll|


2001-07-25 16:08:30 processing result tokens.  marker is  ee
2001-07-25 16:08:30 processing result tokens.  marker is  ae
2001-07-25 16:08:30 inside tds_process_default_tokens() marker is ae
2001-07-25 16:08:30 processing result tokens.  marker is  e5
2001-07-25 16:08:30 processing result tokens.  marker is  fd
Sending packet @ 2001-07-25 16:08:30
0000  06 01 00 08 00 00 00 00                           |........|


Sending packet @ 2001-07-25 16:08:30
0000  06 01 00 08 00 00 00 00                           |........|

TIA!



Ian A. Harding
Programmer/Analyst II
Tacoma-Pierce County Health Department
(253) 798-3549
mailto: ianh AT tpchd.org

>>> camber AT ais.org 07/25/01 02:40PM >>>
Wow,

That is a odd combo...nsfreetds, had to look that one up.  do other apps
exhibit this problem or just nsfreetds?

Brian

On Wed, 25 Jul 2001, Ian Harding wrote:

> Well, I have this up and working, with the unlikely combination of NetBSD 
> 1.5, AOLServer with the nsfreetds module, and on the database side, Sybase 
> SQL Anywhere 5.5.05, Open Server Gateway on an NT 4 server.  We will try it 
> on the Novell 5 server tonight.
> 
> The only problem is that I can't get it to return error codes.  The query 
> executes without complaint, with the rows affected being the only clue it 
> did not work.  I know errors are being generated by the database, they are 
> just not making it back to the app.
> 
> Any ideas?
> 
> 
> 
> Ian A. Harding
> Programmer/Analyst II
> Tacoma-Pierce County Health Department
> (253) 798-3549
> mailto: ianh AT tpchd.org 
> 
> >>> camber AT ais.org 07/05/01 02:30PM >>>
> Yes, but what you have to do depends on the version you run.
> 
> Specifically you must run 5.0.03 or higher.  If running version 5.x you
> must run the "OpenServer Gateway" on the Novell server (it comes with 
> SQL Any).  Somewhere after 5.x (version 6.0 i think but definately 
> by version 7) Sybase made TDS support native, so this is not necessary.
> 
> In any event you must use TDS version 5.0, I have been unable to get 4.2
> to work (I don't know if 4.2 is intended to work or not).
> 
> jkl, can we get this Q added to the FAQ?
> 
> Brian
> 
> On Thu, 5 Jul 2001, Ian Harding wrote:
> 
> > I have been using freetds with AOLServer successfully against MSSQL Server
> > 7.0.  Howerver, I now need to connect to a Sybase SQL Anywhere database
> > and can't seem to make it work.  I am running NetBSD 1.5 and the SQL
> > Anywhere datbase is on a Novell server.  The windows clients that are
> > connecting to the database via odbc are using
> > 
> > "C:\program files\sqlany50\win32\dbclient.exe" envision -x
> > tcpip{host=192.168.100.1}
> > 
> > as a connect string where 'envision' is the name of the database.  
> > 
> > Is it possible to connect to SQL Anywhere using freetds?
> > 
> > Thanks,
> > 
> > Ian
> > 
> 
> 
> ---
> You are currently subscribed to freetds as: [ianh AT tpchd.org] 
> To unsubscribe, forward this message to 
> leave-freetds-132781U AT franklin.oit.unc.edu 
> 
> 
> ---
> You are currently subscribed to freetds as: [camber AT ais.org] 
> To unsubscribe, forward this message to 
> leave-freetds-132781U AT franklin.oit.unc.edu 
> 


---
You are currently subscribed to freetds as: [ianh AT tpchd.org] 
To unsubscribe, forward this message to 
leave-freetds-132781U AT franklin.oit.unc.edu