FreeTDS Development Group

[Brian Bruns <camber AT ais.org>]

Problem is that the call to tds_connect() returns a pointer to TDSSOCKET 
in the dbopen() function.  So that's about all the information that is 
propagated from libtds -> dblib.  I think the other way of not generating 
an error at all had more complaints ;-)

On Mon, 8 Apr 2002, James Cameron wrote:

> mitch AT mdmiller.com wrote:
> > Um ... Isn't Login incorrect a password / user id issue?  Seems like the
> > server responded just fine, and said "go away."
> 
> One might think so, but the connection refused just before that
> generates the login incorrect.  Given that the server address and port
> number are thought to be part of the login information, from an upper
> level one can imagine that login incorrect is meaningful.
> 
> I would prefer if the DB-Library did not say 'Login incorrect' when it
> can't even connect to the server.  ;-)
> 
>