| From: | "Vidas Makauskas" <dbf(at)lindra(dot)lt> |
|---|---|
| To: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>, <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: int8 defined as text in MS Access? |
| Date: | 2002-05-20 09:50:27 |
| Message-ID: | NFBBKEKGNLOACGGMDFKPOEEBCCAA.dbf@lindra.lt |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
> > 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.
:)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gareth Kirwan | 2002-05-20 11:53:01 | Interval to number |
| Previous Message | Inacio dsilva | 2002-05-20 08:26:48 | I want to store a .jpeg file in a table |