Skip site navigation (1) Skip section navigation (2)

Re: psqlODBC Unicode 8.01.02.00 Driver "Overflows" On MS-Access

From: "Tim Clarke" <Tim(dot)Clarke(at)manifest(dot)co(dot)uk>
To: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: psqlODBC Unicode 8.01.02.00 Driver "Overflows" On MS-Access
Date: 2006-03-16 09:58:05
Message-ID: 44D9FC40FD695B4E85F1C59965C27E0FAA4EA8@man3.free2.local (view raw or flat)
Thread:
Lists: pgsql-odbc
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(at)postgresql(dot)org 
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Andreas
> Sent: 15 March 2006 19:39
> To: Randy Yates
> Cc: pgsql-odbc(at)postgresql(dot)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?

Responses

pgsql-odbc by date

Next:From: Bart SamwelDate: 2006-03-16 11:26:14
Subject: Most recent driver aborts transaction after one error
Previous:From: Randy YatesDate: 2006-03-15 21:41:29
Subject: Re: psqlODBC Unicode 8.01.02.00 Driver "Overflows" On MS-Access

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group