I had one of these, too.
The date wasn't correctly formated in the Access table.
It was something like 11/1/106 which should have been entered as
It was a wee bit unpleasant to actually locate the line within the table.
I limited the export to chunks by a numeric primary key. First 1000 then
gradually narrowing down to the bad record.
I'd be cute if the error message contained some form of identifier like
the primary key. On the other hand how should odbc know what column of
some SELECT is an identifier?
Randy Yates schrieb:
> Hi Folks,
> I'm trying to export a table from my MS-Access database to my postgresql
> database. I downloaded and installed the 8.01.02.00 driver on my Win2k
> system, created the datasource. Then when I try to export my table to the
> datasource, I get a single-world message "overflow" and the export aborts.
> I traced the cause of the overflow to a column that is in MS-Access's
> date/time format.
> Is this a known bug? Is there a workaround?
In response to
pgsql-odbc by date
|Next:||From: Dave Page||Date: 2006-03-15 20:07:27|
|Subject: Future development|
|Previous:||From: Augusto Meza Lizardi||Date: 2006-03-15 17:40:41|
|Subject: Problems with ñÑéíóúá in XP Professional and not under XP Home|