Received: from trends.net (root@NS.TRENDS.CA [209.47.148.2]) by hub.org (8.9.3/8.9.3) with ESMTP id AAA24748 for ; Fri, 2 Jul 1999 00:33:50 -0400 (EDT) (envelope-from mooney@stratfor.com) Received: from deliverator.io.com (root@deliverator.io.com [199.170.88.17]) by trends.net (8.8.8/8.8.8) with ESMTP id AAA05058 for ; Fri, 2 Jul 1999 00:24:49 -0400 (EDT) Received: from jutland (as3-dialup-01.io.com [206.224.81.97]) by deliverator.io.com (8.9.3/8.9.3) with SMTP id XAA08024 for ; Thu, 1 Jul 1999 23:23:24 -0500 Message-ID: <005c01bec442$278b9fa0$6151e0ce@jutland> Reply-To: "Michael Mooney" From: "Michael Mooney" To: Subject: pgsqlODBC + Flick's Authentix Date: Thu, 1 Jul 1999 23:20:01 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by hub.org id AAA24749 The Authentix executable seems to try to pull or create a DSN connection string from the Registry? At any rate, it successfully does that for most of the packaged ODBC drivers, but fails to do anything with pgsqlodbc. This leaves me with a blank DSN connection string field. Any pointers on filling this out, or where to look for details? Has anyone else succeeded in getting Authentix to work with pgsqlodbc?