| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Patrick Hatcher" <PHatcher(at)macys(dot)com>, <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: int8 defined as text in MS Access? |
| Date: | 2002-05-17 07:20:47 |
| Message-ID: | 214E9C0A75426D47A876A2FD8A07426E0B3998@salem.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
> -----Original Message-----
> From: Patrick Hatcher [mailto:PHatcher(at)macys(dot)com]
> Sent: 16 May 2002 23:22
> To: pgsql-odbc(at)postgresql(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Henshall, Stuart - WCP | 2002-05-17 10:16:12 | Re: int8 defined as text in MS Access? |
| Previous Message | Patrick Hatcher | 2002-05-16 22:22:27 | int8 defined as text in MS Access? |