FreeTDS Development Group

[Jeff Honey <jhoney AT psmanagement.net>]

Indeed. Worked like a charm. Now that I have been "shown the light", looking
BACK at the user guide...I can see where server= is not servername=, *DOH*.
I tried forming a more perfect, freetds.conf-less, odbc.ini file but I was
getting stumped by the servername= and pared everything back to a bare
minimum.

Perhaps a large mallet to bonk the boneheads who can't read ALL the
documentation the first time would prove better instruction?  ;-)

§ -----Original Message-----
§ From: Lowden, James K [mailto:LowdenJK AT bernstein.com]
§ Sent: Tuesday, April 15, 2003 16:20
§ To: 'FreeTDS Development Group'
§ Subject: RE: [freetds] unixODBC failing to connect.
§ 

§ > ODBC.INI:
§ > [testserver]
§ > Driver          = TDS
§ > Description     = Northwind sample database
§ > Trace           = yes
§ > Servername      = 192.168.1.15
§                       ^^^^^^^^^^^^  should be "testserver".
§ > Database        = Northwind
§ > UID             = sa
 
§ The ODBC driver reads ODBC.INI to get the "real" servername, 
§ which it passes
§ to FreeTDS (which in turn looks up the ip address of the name 
§ in the "host"
§ entry).  
§ You don't *have* to use both these files.  We tried to make 
§ that clear in
§ the User Guide.  http://www.freetds.org/userguide/x1853.htm.  
§ Anything you
§ can do to make that more understandable would be welcome. :-)