| From: | "Tobias Wendorff" <tobias(dot)wendorff(at)tu-dortmund(dot)de> |
|---|---|
| To: | "Jan Wieck" <jan(at)wi3ck(dot)info> |
| Cc: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp>, pgsql-odbc(at)lists(dot)postgresql(dot)org |
| Subject: | Re: NUMERIC type makes trouble in MS Access |
| Date: | 2018-05-27 16:35:59 |
| Message-ID: | 1f71eedeb0316b4de796d0a49ecdbd2f.squirrel@webmail.tu-dortmund.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Am So, 27.05.2018, 05:18 schrieb Jan Wieck:
> Anything that is exact precision in the database should never
> be handled as "double" in any driver. That is a serious bug and
> a possible violation of accounting laws in many countries.
So SQL_NUMERIC is DOUBLE? Sorry, I'm not an insider ;)
Access supports DECIMAL file type with a range from -9.999... x 10^27
to +9.999... x 10^27 while DOUBLE goes from -1.797 x 10^308 to
1.797 x 10^308.
Actually, older Access had problems with DECIMAL fields in the past,
maybe those got fixed already?
Best regards,
Tobias
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Danny Severns | 2018-05-27 19:35:53 | RE: NUMERIC type makes trouble in MS Access |
| Previous Message | Jan Wieck | 2018-05-27 03:18:12 | Re: NUMERIC type makes trouble in MS Access |