My best guess is that there is nothing actually wrong with the internal
workings of access, odbc driver and postgresql. You problem might be
that one of the rows you are trying to export contains a value that is
too big for the field you are trying to insert it into. Perhaps you
should check your data definitions and make sure you have specified the
correct scale and precision on any numeric (decimal) fields. The same
goes for varchar, integers, etc.
Access tends to throw back cryptic error messages at you and in my
(humble) experience it has always been a datatyping error or a foreign
key constraint that I have broken, but this may not be the case for you.
Maybe it helps, maybe it doesn't, but it's something for you to think about.
> Hi folks. I tried searching this list's archives for this problem but
> came up short. I have a fairly large table in MS Access 2000 (33
> cols, 3270 rows) that I'm trying to export to PostgreSQL 7.4.3. When
> I clip the table to only about 100 rows, the export runs fine, but
> when I try to export the whole thing, I get an error window that says
> only "Overflow." This process generates the following error in my
> postgresql.log file:
In response to
pgsql-odbc by date
|Next:||From: Janet Borschowa||Date: 2004-09-16 21:49:14|
|Subject: Re: ODBC SQLSetPos Delete problem|
|Previous:||From: Ken-ichi||Date: 2004-09-16 20:48:05|
|Subject: Access export overflow|