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.
