Received: from mail.toppoint.de (LaForge.toppoint.de [195.244.243.6]) by hub.org (8.9.3/8.9.3) with SMTP id NAA02541 for ; Wed, 22 Sep 1999 13:33:51 -0400 (EDT) (envelope-from feki.toppoint.de!marten@toppoint.de) Received: by mail.toppoint.de (Smail3.1.29.1) id ; Wed, 22 Sep 99 19:33 MET DST Received: (from marten@localhost) by feki.toppoint.de (8.9.3/8.9.3) id HAA01596; Wed, 22 Sep 1999 07:14:16 -0700 From: marten@feki.toppoint.de Message-Id: <199909221414.HAA01596@feki.toppoint.de> Subject: Re: [INTERFACES] ODBC-Interfaces - connection options ? Error ! In-Reply-To: from Nuchanach Klinjun at "Sep 21, 1999 9:46:53 am" To: nuchk@inet.co.th (Nuchanach Klinjun) Date: Wed, 22 Sep 1999 07:14:15 -0700 (MST) Cc: jyry@laserle.fi, pgsql-interfaces@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL47 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit > On Mon, 20 Sep 1999, Jyry Kuukkanen wrote: > > > >Hello, > > > > > I've a problem in the very first state of the odbc-connection from a > > > NT 4.0, SP4 and my ODBC driver for PostgreSQL and I get the following > > > output from my ODBC driver:. > > > > > My simple question: why !? What is the "unknown connect option" ? > > > > > > Unfortunately, I can't help you, but I've run into same feature (?) using > > Lotus Approach as a client. > > > > I think the key to the problem is in the log file about here: > > > > SQLDriverConnect(out)='DSN=PITPSQL;plaahplaah.....; > ^^^^^^^^^^^^^^^^^ > > I think so also because I never seen the option 'plaahplaah' anywhere,the > syntax to sent the connection parameter should be in the list below..(the > list below is not the full option, you can see all about it in tne psqlodbc log file) > Actually the original posting came from me - some weeks ago. The reason for this has been found. The development environment I used (IBM VisualAge/ST) uses "special" ODBC manager and drivers from Intersolv. This special handling is used to check wether the user has a special license to use the ODBC drivers and manager. The checking was done within IBM Smalltalk and I´ve found the call, where the special option has been set. Removing the call and I was able to use the PostgreSQL driver. BUT: I´ve used several third-party odbc drivers and they all work well - only the PostgreSQL drivers returns an error - perhaps the behaviour of the driver should be changed ! Marten