Thread: psqlODBC Unicode 8.01.02.00 Driver "Overflows" On MS-Access Dates
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? -- % Randy Yates % "I met someone who looks alot like you, %% Fuquay-Varina, NC % she does the things you do, %%% 919-577-9882 % but she is an IBM." %%%% <yates@ieee.org> % 'Yours Truly, 2095', *Time*, ELO http://home.earthlink.net/~yatescr
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? 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? >
maps.on@gmx.net (Andreas) writes: > 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. Yep! Mine was similar! Thank you, Andreas! > 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? It could certainly emit each row of the table and identify the offending field. -- % Randy Yates % "Rollin' and riding and slippin' and %% Fuquay-Varina, NC % sliding, it's magic." %%% 919-577-9882 % %%%% <yates@ieee.org> % 'Living' Thing', *A New World Record*, ELO http://home.earthlink.net/~yatescr