Received: from bastion.solipsys.com (bastion.solipsys.com [209.117.190.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id NAA72118
	for <pgsql-interfaces@postgreSQL.org>;
	Mon, 23 Aug 1999 13:35:19 -0400 (EDT)
	(envelope-from byronn@solipsys.com)
Received: from solipsys.com ([209.117.190.166])
	by bastion.solipsys.com (8.9.1a/8.9.1) with ESMTP id NAA09287;
	Mon, 23 Aug 1999 13:34:37 -0400 (EDT)
Message-ID: <37C18608.D5D0AE6F@solipsys.com>
Date: Mon, 23 Aug 1999 13:34:00 -0400
From: Byron Nikolaidis <byronn@solipsys.com>
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Michael Doyle <relyod@co-operation-ireland.ie>
CC: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Access 2000
References: <3.0.5.32.19990823163802.0079f180@199.107.2.1>
	<3.0.5.32.19990823182940.007ac100@199.107.2.1>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Michael Doyle wrote:

> At 12:16 23/08/99 -0400, Byron Nikolaidis wrote:
> >
> >Do you see any error messages, either on screen or in any of the logfiles?
> >
> >Byron
>
> Byron,
>
> In the log files I see access issues the following:
>         query 'SELECT Config, nValue from MSysConf'
>
> to which the server responds
>         'ERROR: msysconf: Table does not exist.'
>
> In other words, Access seems to be looking for a configuration table
> which PostgreSQL does not have. When it can't find it, Access then
> refuses to do any more.
>

This is normal and has always been there.  It is an optional file to configure
some things in Access.

Can you attach both the psqlodbc.log and sql.log files?  There might be a
subtle thing in how it gets the tables.

Byron