Received: from u1.abs.net (root@u1.abs.net [207.114.0.131]) by hub.org (8.9.2/8.9.1) with ESMTP id MAA32027 for ; Thu, 11 Feb 1999 12:17:22 -0500 (EST) (envelope-from daveh@insightdist.com) Received: from insightdist.com (root@localhost) by u1.abs.net (8.9.0/8.9.0) with UUCP id MAA27677 for pgsql-interfaces@postgreSQL.org; Thu, 11 Feb 1999 12:10:50 -0500 (EST) Received: from ceodev by insightdist.com (AIX 3.2/UCB 5.64/4.03) id AA17536; Thu, 11 Feb 1999 09:34:41 -0500 Received: from daveh by ceodev (AIX 4.1/UCB 5.64/4.03) id AA36698; Thu, 11 Feb 1999 09:34:41 -0500 Message-Id: <36C2EAA0.8DEE0FAB@insightdist.com> Date: Thu, 11 Feb 1999 09:35:12 -0500 From: David Hartwig Organization: Insight Distribution Systems X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en Mime-Version: 1.0 To: kk@kdschmid.de Cc: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] ODBC - MSysConf References: <36C344C5.4A28@kdschmid.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Karsten Kaus wrote: > ok, in general it seems to be possible to connect Access97 ( not Access > 2.0! ?right? ) to postgres. I recall someone doing this successfully. The key here is that it needs to be running on Win95, Win98, or NT. > > It works on ONE of my Computers in the office (486). On that computer > I cannot start the 32Bit-ODBC in the systemconfiguration, but I can > create DSNs within Access97, and I get connected to any postgres- > database I wish (tried only 2). > On my Pentium in the office and on ALL machines at home I get the > error 4307, that there is a Table called MSysConf on my server but > it does not have the expected format. You do not need this table on the server. The driver will report it as an error in the log file, but it should not be a problem to the application. Activate the CommLog in the driver settings and send a copy of the errant session. Its located in C:\psqlodbc*.log. > > I searched for this table using grep and pg_dumpall as well as psql \dS > and could not find anything. So I created one as described in the > MSAccess-Help, but this didn't help. Still the fomat was invalid. > I do not want to use this table anyway ( do I? ), so what to do? > I would drop the table unless you know what you are doing with MSysConf. At least until you get on solid footing. It's improper configuration may cause other problems.