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
