Doing a .csv import and getting this message at row 1,167,918.

I see from googling the archives of this newsgroup that people often
see this error but that it may actually occur a long ways away from
the reported row.

I've got a lot of rows.

Any great ideas as to how to search for it?

I'm using a great tool in fileviewer.com that lets me get right down
to the row# listed, but the data there looks fine, in ascii and hex.

This is production code that has been running successfully for months
and years, but we got failures in the same step running from separate
downloads on separate machines, so something is hinky in the data, if
I can just find it. 300mb of csv ...

Thanks.

Josh

Well, I never did find a problem with the data, but I did find the
file imports cleanly on another server running SP3a instead of SP2, it
also imports cleanly if I use the ODBC/other connection instead of the
normal OLEDB connection, ... even though they use the same version of
the flatfile driver underneath.

Go figure.

J.



On Thu, 25 May 2006 11:45:18 -0700, jxstern <jxstern (AT) wherever (DOT) com>
wrote: