FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
> Sent: February 26, 2003 1:57 AM
> Il mer, 2003-02-26 alle 06:30, James K. Lowden ha scritto:
> > On Tue, 25 Feb 2003 13:46:35 -0800, Peter Harvey
> > <pharvey AT codebydesign.com> wrote:
> > > I can update the unixODBC section if you want - let me know.
> > 
> > Probably easiest is
> > to let Freddy and me rearrange things, then you can 
> > applify/correct our New & Improved version.  
> 
> I check index and seem good.
> However I don't know sgml/docbook very  well... I'm not able to code
> such think, I can write some help but not sections and similar. I saw
> time ago a docbook split in parts. Is possible to split our doc?
> 
> Perhaps is better:
>   Building
>     Common stuff (make sense?)
>     unixODBC
>     iODBC
>   Installing
>     by rpm, by source
>     odbcinst.ini (here or in configure?)
>   Configuring
>     File used, where...

Hmm.  That suggests integrating the ODBC and RPM instructions into the main
Build and Install sections.  That's a good idea, because -- unlike Perl et.
al. -- the ODBC driver manager is part of those tasks.  

Don't worry about SGML tags or English.  Say what you mean, organized how
you want.  I can mark it up later, but I can't write something I don't
understand.  Well, I *can*, but I'm not sure how useful it would be, as a
guide.  

Of course, the more familiar you become with SGML, the easier it is for me,
but that will come over time as you gain experience.  No need to force the
issue.  

> > > > $ isql -v server user password
> > > > [unixODBC]Client unable to establish connection
> > > > [ISQL]ERROR: Could not SQLConnect
> > > 
> > > In theory more information should be coming back from ODBC. 
> 
> Error I return is "Client unable to establish connection". I can't be
> more specific cause tds_connect do not return any suitable information
> on type of error (just success or fail)

You may recall tds_connect() is due for an overhaul, by me.  I'm going to
split out:

1.  Reading the configuration files (local).
2.  Determining the server's ip address (DNS).
3.  Connecting to the port (network).
4.  Logging in (TDS).  

I think, however, you already have some information you're not conveying.
If you failed at #4, there's a message from the server.  If you failed
before that, you have the servername, and its hostname and address.  

So your messages could be:

        'FreeTDS:  Client unable to establish connection to "Servername" on
machine "hostname" at address "192.168.1.17" ', or 
 
        'FreeTDS:  Login to server "Servername" failed for user "Username"
'.  

Those would be helpful, I think.  

<rant> I just got a message from my NT box: "The referenced account is
currently locked out and may not be logged on to."  What program?  What
account?  Logged on to ... where?  </rant>

--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.