Message-Id: <36388340.5A6EFA0C@insightdist.com>
Date: Thu, 29 Oct 1998 10:01:20 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Mime-Version: 1.0
To: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Cc: scampbell@lear.com, "Cary O'Brien" <cobrien@access.digex.net>,
	Postgres Interfaces Mailing List <pgsql-interfaces@postgresql.org>
Subject: Re: Standalone driver for Unix
References: <199810291349.IAA00618@scampbell.learcorp.com>
	<36387FAD.B55A7BB5@alumni.caltech.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Thomas G. Lockhart wrote:

> scampbell@lear.com wrote:
> >
> > I had one other interesting thing with the Postgresql ODBC driver.
>   I don't know much of the internal's of ODBC but here's what I'm
>   wondering...
> >
> > When I use an extended datatype (let's say one for ipaddress for
>   instance) and then use MS Access to open the table via ODBC it
>   complains that the 'ipaddress' is an unknown type.  I have clicked a
>   box in creation of the ODBC ini file (or the .DSN file actually in the
>   case of MS) that says (something similar to) 'Treat unknown datatypes
>   as LongVarChar' but it seems to have no effect turned on or off.  Does
>   our drive not support this?  Is MS just show it normal 'excellence in
>   programming'?  Any ideas?
> >

Are you trying to use this 'ipaddress' field as a key field?  If so, you
must NOT check the Treat unknown datatypes as LongVarChar.  The reason is
Access can't have a unique index on a field that is over 255 characters,
which is the default max length for a longvarchar.

Try unchecking the option, then you *must* re-link the table in Access to
see if it worked.    Also, Make sure the size for "Max Varchar" is set to
the default of 254.

Byron