Received: from bastion.solipsys.com (bastion.solipsys.com [209.117.190.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id JAA74662
	for <pgsql-interfaces@postgreSQL.org>;
	Tue, 29 Jun 1999 09:34:51 -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 JAA11440;
	Tue, 29 Jun 1999 09:33:57 -0400 (EDT)
Message-ID: <3778CBA1.CF52B12A@solipsys.com>
Date: Tue, 29 Jun 1999 09:35:29 -0400
From: Byron Nikolaidis <byronn@solipsys.com>
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Moray McConnachie <Moray.McConnachie@computing-services.oxford.ac.uk>
CC: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] ODBC and Access 2000: linked tables problem
References: <EXECMAIL.990629114330.D@moraypc.computing-services.oxford.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Moray McConnachie wrote:

> I was hoping someone could help me out with this, although
> it's probably more of an Access problem than a Postgres
> ODBC one...
>
> I am using Access 2000 and postgres, with the postgres ODBC
> drivers.
>
> Everything worked fine under Access 97.
>
> Importing tables from the ODBC connection is fine.
> *Linking* is fine as far as the table selection and the importing of
> fields and selecting of unique index goes.
>
> However, when I try and open the linked table, it says "Access cannot
> open the table in datasheet view". Nor can it access it via a query. I
> have also tried hardcoding the table in a way which worked in Access 97
> (code appended below), and it fails in exactly the same way.
>
> SQL tracing appears to reveal that when a table is opened,
> Access doesn't even get as far as putting a command to the
> remote database.
>

Send the sql trace log.

Byron