Thread: 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 Patrick Hatcher Macys.Com
> -----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.
There isn't an int8 in Access.
The largest int is long which is equivalent to int4.
Cheers,
- Stuart
> -----Original Message-----
> From: Patrick Hatcher [mailto:PHatcher@macys.com]
> Sent: 16 May 2002 23:22
> To: pgsql-odbc@postgresql.org
> Subject: 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
>
> Patrick Hatcher
> Macys.Com
>
>
>
>
Dave Page wrote: > > > -----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. Unfortunately int8 -> SQL_BIGINT doesn't work well even with ODBC 3.0 driver using MS Access. However int8 -> SQL_NUMERIC seems to work with both 2.5 and 3.0 driver. Try the snapshot dll at http://w2422.nsk.ne.jp/~inoue/. regards, Hiroshi Inoue http://w2422.nsk.ne.jp/~inoue/
> > 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. > > Unfortunately int8 -> SQL_BIGINT doesn't work well > even with ODBC 3.0 driver using MS Access. However > int8 -> SQL_NUMERIC seems to work with both 2.5 and > 3.0 driver. Try the snapshot dll at > http://w2422.nsk.ne.jp/~inoue/. > > regards, > Hiroshi Inoue Would be very nice option INT8 as FLOAT8. :)
Thanks.
Hiroshi, which driver is the snapshot dll?
Patrick Hatcher
Macys.Com
Legacy Integration Developer
415-932-0610 office
HatcherPT - AIM
Hiroshi Inoue
<Inoue@tpf.co. To: Dave Page <dpage@vale-housing.co.uk>, Patrick Hatcher
jp> <PHatcher@macys.com>
cc: pgsql-odbc@postgresql.org
05/19/2002 Subject: Re: [ODBC] int8 defined as text in MS Access?
11:48 PM
Dave Page wrote:
>
> > -----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.
Unfortunately int8 -> SQL_BIGINT doesn't work well
even with ODBC 3.0 driver using MS Access. However
int8 -> SQL_NUMERIC seems to work with both 2.5 and
3.0 driver. Try the snapshot dll at
http://w2422.nsk.ne.jp/~inoue/.
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
Patrick Hatcher wrote:
>
> Thanks.
> Hiroshi, which driver is the snapshot dll?
If you aren't a multibyte guy
psqlodbc.dll (version 7.02.0001)
else
psqlodbc.dll(the multibyte version).
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
That worked.
Thank you
Patrick Hatcher
Macys.Com
Legacy Integration Developer
415-932-0610 office
HatcherPT - AIM
Hiroshi Inoue
<Inoue@tpf.co. To: Patrick Hatcher <PHatcher@macys.com>
jp> cc: Dave Page <dpage@vale-housing.co.uk>, pgsql-odbc@postgresql.org
Subject: Re: [ODBC] int8 defined as text in MS Access?
05/20/2002
04:31 PM
Patrick Hatcher wrote:
>
> Thanks.
> Hiroshi, which driver is the snapshot dll?
If you aren't a multibyte guy
psqlodbc.dll (version 7.02.0001)
else
psqlodbc.dll(the multibyte version).
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/