Whenever I get these I write a tiny "stuff one record in and tell me if
it errors" iteration. Just leave that running and get on with something
else productive.
Tim Clarke
> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Andreas
> Sent: 15 March 2006 19:39
> To: Randy Yates
> Cc: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] psqlODBC Unicode 8.01.02.00 Driver
> "Overflows" On MS-Access
>
>
> 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
> 1/11/2006.
>
> 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?
