Re: [INTERFACES] MS Access & PsqlODBC: Invalid field name 'name'

From: Byron Nikolaidis <byronn(at)insightdist(dot)com>
To: Ewan Mellor <em(at)nexus(dot)co(dot)uk>
Cc: PostgreSQL Interfaces <pgsql-interfaces(at)postgreSQL(dot)org>
Subject: Re: [INTERFACES] MS Access & PsqlODBC: Invalid field name 'name'
Date: 1998-05-12 14:34:38
Message-ID: 35585DFE.6FE69EF@insightdist.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

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.

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Byron Nikolaidis 1998-05-12 14:37:08 Re: [INTERFACES] Re: NEW ODBC DRIVER
Previous Message Tom Lane 1998-05-12 14:30:53 Re: [HACKERS] Re: [PATCHES] Try again: S_LOCK reduced contentionh]

Browse pgsql-interfaces by date

  From Date Subject
Next Message Byron Nikolaidis 1998-05-12 14:37:08 Re: [INTERFACES] Re: NEW ODBC DRIVER
Previous Message The Hermit Hacker 1998-05-12 13:26:36 Auth db