Re: int8 defined as text in MS Access? - Mailing list pgsql-odbc

From Dave Page
Subject Re: int8 defined as text in MS Access?
Date
Msg-id 214E9C0A75426D47A876A2FD8A07426E0B3998@salem.vale-housing.co.uk
Whole thread Raw
In response to int8 defined as text in MS Access?  ("Patrick Hatcher" <PHatcher@macys.com>)
List pgsql-odbc

> -----Original Message-----
> From: Patrick Hatcher [mailto:PHatcher@macys.com]
> Sent: 16 May 2002 23:22
> To: pgsql-odbc@postgresql.org
> Subject: [ODBC] int8 defined as text in MS Access?
>
>
> ODBC ver 7.1.10 and 7.2.0
> Is it correct for an int8 value to be considered as a text
> field when I link a table in Access?  If so, just out of
> curiosity, why is this so? TIA

Yes, this has been the subject of discussion a number of times in the
past. MS ADO (and other technologies) crash or get upset if the driver
returns SQL_BIGINT for an int8 from the ODBC 2.5 driver, because it
expects SQL_VARCHAR. With the (beta) ODBC 3.0 driver, you get an
SQL_BIGINT which should work fine.

Regards, Dave.

pgsql-odbc by date:

Previous
From: "Patrick Hatcher"
Date:
Subject: int8 defined as text in MS Access?
Next
From: "Henshall, Stuart - WCP"
Date:
Subject: Re: int8 defined as text in MS Access?