| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tobias Wendorff <tobias(dot)wendorff(at)tu-dortmund(dot)de> |
| Cc: | Danny Severns <Danny(at)eidl-sw(dot)com>, Jan Wieck <jan(at)wi3ck(dot)info>, "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp>, "pgsql-odbc(at)lists(dot)postgresql(dot)org" <pgsql-odbc(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: NUMERIC type makes trouble in MS Access |
| Date: | 2018-05-28 04:58:37 |
| Message-ID: | CAMsr+YGbpVweP5=UNUAhieB3Qo+-D9tsXDvb_wO=sNh2SujuCw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
On 28 May 2018 at 11:50, Tobias Wendorff <tobias(dot)wendorff(at)tu-dortmund(dot)de>
wrote:
> Here an update:
>
> by default, MS Access sets linked tables with "unlimited" NUMERIC
> to DECIMAL with "precision: 28" and "decimals: 6" (MS Access names).
> Trying to read a value [INSERT INTO public.demo VALUES (1.0 / 3)]
> breaks with an error.
>
> When creating the column using NUMERIC(28, 24), MS Access shows this:
> "precision: 28" and "decimals: 24". And there's no error.
>
> Funny, when creating the column using NUMERIC(32, 28), MS Access
> interprets it as TEXT with field length 32.
>
> NUMERIC(28,27) is the last column type, MS Access can read as DECIMAL.
>
> A view on an "unlimited" NUMERIC with casting ::NUMERIC(28, 24)
> is accepted by Access. So it seems like I need to create a VIEW as a
> work-around.
>
Sounds like this is something the ODBC driver could work around, by
exposing the option to clamp the reported NUMERIC scale and precision.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Inoue, Hiroshi | 2018-05-28 07:17:22 | Re: NUMERIC type makes trouble in MS Access |
| Previous Message | Tobias Wendorff | 2018-05-28 03:50:21 | RE: NUMERIC type makes trouble in MS Access |