| From: | "Tobias Wendorff" <tobias(dot)wendorff(at)tu-dortmund(dot)de> |
|---|---|
| To: | "Danny Severns" <Danny(at)eidl-sw(dot)com> |
| Cc: | "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 03:50:21 |
| Message-ID: | f51780612e5990c605efb86ec0417121.squirrel@webmail.tu-dortmund.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2018-05-28 04:58:37 | Re: NUMERIC type makes trouble in MS Access |
| Previous Message | Tobias Wendorff | 2018-05-28 02:13:06 | Re: NUMERIC type makes trouble in MS Access |