Sender: em
Message-ID: <3558923F.64DD0786@nexus.co.uk>
Date: Tue, 12 May 1998 19:17:35 +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>
	<355877AC.72D6D289@nexus.co.uk> <3558803F.72A8D0F@insightdist.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Byron Nikolaidis wrote:
> 
> Ewan Mellor wrote:
> 
> > 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.
> >
> 
> Wait, I think I have it!
> 
> Access will not allow you to index on LongVarchar data types OR character types
> that are longer than 254 characters (255 with null).  I bet these columns you
> are having trouble with are Postgres TEXT types or varchars/chars that are over
> 254.
> 
> Check out the odbc driver setup options dialog.  You can map TEXT fields to
> plain varchar; then set the LongVarChar size to 254, and it should work!

Well done indeed!  With that you have elevated yourself to the higher
echelons of gurudom.  Congratulations. :-)

One for the FAQ methinks...

Ewan.