Sender: em
Message-ID: <355877AC.72D6D289@nexus.co.uk>
Date: Tue, 12 May 1998 17:24:12 +0100
From: Ewan Mellor <em@nexus.co.uk>
Organization: Nexus Electronics
MIME-Version: 1.0
To: PostgreSQL Interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: [INTERFACES] MS Access & PsqlODBC: Invalid field name 'name'
References: <35582955.5F014F7B@nexus.co.uk> <35585DFE.6FE69EF@insightdist.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Byron Nikolaidis wrote:
> 
> Set the "Recognize Unique Indexes" to disabled (unchecked).
> Then, when Access asks you for a unique field, don't select anything and
> hit ok.
> Thus, you are telling access you have no index.
> 
> This should allow you to get at your data until we figure out what "name"
> has to do with this problem.

I tried that, but it does not seem to help.  Perhaps Access is asking
for the index information of its own accord?

I have just discovered it also objects to:

rt_url,
url,
genre,
name_en,
stored,
stored1,
address, and
server.

Note that many have succeeded.  Curiouser and curiouser...

Thanks, Byron, both for your help and for what looks like it will be a
really useful driver.  If only the whole planet didn't use Access...

> Byron
> 
> Ewan Mellor wrote:
> 
> > I am using Byron's ODBC driver (version .0239 downloaded today) with
> > Access 7.00 under Win95 with Postgres 6.3.  I am trying to link tables
> > into Access.  Most tables work fine, but any field with the name 'name'
> > or 'sortname' or even 'garbagename' may not be used as part of an
> > index.  This occurs whether the index is picked up automatically by the
> > driver, or if you are asked to choose a unique field by Access.
> >
> > Can this be fixed?  As a workaround, could the driver optionally not
> > tell the client application about indices?  In this way, I could tell
> > Access to ignore them and then (I think) I would be able to get at my
> > data.
> >
> > Ewan Mellor.