RE: (no subject)

> From: dirtydozen@xxxxxxxxx [mailto:dirtydozen@xxxxxxxxx]
> Sent: July 28, 2003 1:59 PM
> 
> I have a problem connecting to a MSSQL 2000 server
> 
...
> i also tried to give some sql command and they work...
> 
> ok that's ok.. So i tried to connect with 
> 
> isql -v TDS <username> <password> and it doesn't work:
> 
> [unixODBC]Il contesto di database è stato sostituito con 'dipendenti'.
> [unixODBC]Login incorrect.
> [unixODBC]Client unable to establish connection

You're right, you connected to the server.  I think that first message is
Italian for "Changed database to 'dipendenti'"?  It came from the server.

The log also shows you get back good results:

> 2003-07-28 19:02:15.355035 inside 
> tds_process_default_tokens() marker is e3(ENVCHANGE)
> 2003-07-28 19:02:15.355098 inside 
> tds_process_default_tokens() marker is ab(INFO)
> 2003-07-28 19:02:15.355138 inside 
> tds_process_default_tokens() marker is e3(ENVCHANGE)
> 2003-07-28 19:02:15.355175 inside 
> tds_process_default_tokens() marker is e3(ENVCHANGE)
> 2003-07-28 19:02:15.355204 inside 
> tds_process_default_tokens() marker is fd(DONE)

If you hadn't logged in, you would have seen an aa(ERROR) token instead.

You're not the first fellow to report this.  I suspect we're surprising
unixODBC's isql somehow.  Perhaps our return code isn't right, or perhaps
it's not expecting our messages.  

I think you're using the 0.61 release?  And what version of unixODBC?  I
think it's likely the current versions of FreeTDS and unixODBC *do* work
together.  Perhaps you happen to have a bad mix.  

I don't use ODBC myself.  Can anyone else confirm this?  

--jkl
-----------------------------------------
The information contained in this transmission may contain privileged and 
confidential information and is intended only for the use of the person(s) 
named above. If you are not the intended recipient, or an employee or agent 
responsible for delivering this message to the intended recipient, any review, 
dissemination, distribution or duplication of this communication is strictly 
prohibited. If you are not the intended recipient, please contact the sender 
immediately by reply e-mail and destroy all copies of the original message. 
Please note that we do not accept account orders and/or instructions by e-mail, 
and therefore will not be responsible for carrying out such orders and/or 
instructions.