| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | albert <skarbat(at)gmail(dot)com> |
| Cc: | aihtdikh(at)gmail(dot)com, pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: MSAccess to postgres on Windows Currency type problem |
| Date: | 2011-09-12 23:08:03 |
| Message-ID: | 17626.1315868883@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
albert <skarbat(at)gmail(dot)com> writes:
> I could csv-export the table correctly, so no corruption apparently. I found
> a registry key called "LocksPerPage" that belongs to MS Office, after
> increasing it I was able to translate MSAcces Currency type to Integer
> successfully. Exporting through ODBC right after that was also successful.
> However that doesn't ring me a bell on how one can automagically export an
> MSAccess table through postgres odbc when having a column with Currency data
> type.
It looks like you're using a locale in which the decimal separator is
comma rather than period. Perhaps changing some locale setting on the
MSAccess side would help?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arvind N | 2011-09-22 07:10:58 | psqlodbc-09.00.0310 Crash issues with aggregate function based queries.. specifically SUM and AVG. |
| Previous Message | albert | 2011-09-12 19:35:33 | Re: MSAccess to postgres on Windows Currency type problem |