Received: from eta.ece.rice.edu (ece.rice.edu [128.42.4.34])
	by hub.org (8.9.2/8.9.1) with ESMTP id RAA40735
	for <pgsql-interfaces@postgresql.org>;
	Mon, 8 Mar 1999 17:04:48 -0500 (EST)
	(envelope-from reedstrm@rice.edu)
Received: from rice.edu (wallace.ece.rice.edu [128.42.12.154])
	by eta.ece.rice.edu (8.9.0/8.9.0) with ESMTP id QAA29877
	for <pgsql-interfaces@postgreSQL.org>;
	Mon, 8 Mar 1999 16:00:07 -0600 (CST)
Sender: reedstrm@ece.rice.edu
Message-ID: <36E44975.1379348E@rice.edu>
Date: Mon, 08 Mar 1999 16:04:37 -0600
From: "Ross J. Reedstrom" <reedstrm@rice.edu>
Organization: NSBRI
X-Mailer: Mozilla 4.06 [en] (X11; U; Linux 2.0.34 i686)
MIME-Version: 1.0
To: pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] Re: Read-only in MSAccess
References: <99030816523400.00644@schwa>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I've noticed this affect. Has anyone run traces of the connection, to
see if Access tries to determine the primary key from the backend? Does
this requirement go away if you (manually) set the 'relhaspkey' bool in
pg_class for the table?  I'd do all this testing myself, but my NT test
box got taken away (yeay! boo! I'm so conflicted...)

Ross

Ben Gunter wrote:
> 
> (Original message was lost.  Oops.)
> 
> I was fiddling around with Access and the ODBC driver this morning and
> discovered that Access will not allow you update ODBC sources unless you pick
> at least one field (up to ten) as a unique index.  Otherwise, it's read-only.
> 
> Hope this helps.
> 
> -Ben

-- 
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu> 
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St.,  Houston, TX 77005