Re: NUMERIC type makes trouble in MS Access

From: "Tobias Wendorff" <tobias(dot)wendorff(at)tu-dortmund(dot)de>
To: "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp>
Cc: "Craig Ringer" <craig(at)2ndquadrant(dot)com>, "Jan Wieck" <jan(at)wi3ck(dot)info>, pgsql-odbc(at)lists(dot)postgresql(dot)org
Subject: Re: NUMERIC type makes trouble in MS Access
Date: 2018-05-29 00:55:57
Message-ID: 5d0408017ead8cfc409e3de5ce115c77.squirrel@webmail.tu-dortmund.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Interesting detail: It's not an Access problem.

I've tested it with Python and Libre Office Base. NUMERIC without
precision gets set to 28,6 => like in Access.

Would it perhaps better to use MEMO instead of VARCHAR?
MEMO allows more than 8,000 chars in "Base" and some gigabytes in
Access.

But there's not enough space for an additional toggle switch :(

Browse pgsql-odbc by date

  From Date Subject
Next Message Inoue, Hiroshi 2018-05-29 01:39:15 Re: NUMERIC type makes trouble in MS Access
Previous Message Tobias Wendorff 2018-05-29 00:43:49 Re: NUMERIC type makes trouble in MS Access