I am getting the following error:

"Too many columns found in the current row; non-whitespace characters were
found after the last defined column's data. "

It seems a few people (going by google/newsgroup searches) have encountered
this, but none of which had a very clear resolution.

I am trying to import file into a SQL table.
- Its a pipe/vertical bar delimited
- The file is approx 48mb,
- contains 117,000 odd rows
- has {cr}{lf} as row delimeter

I am running SQL 2000 Sp3.

Any help would be greatly appreciated.

Correction, SP4

In message <#VoZEXIYFHA.2572 (AT) TK2MSFTNGP14 (DOT) phx.gbl>, Ben Rum
<bundyrum75 (AT) yahoo (DOT) com> writes
Basically this means the file format is invalid. You probably have
additional data on a line, after DTS has found all of the expected
number of column delimiters. It expects the next delimiter to be the row
delimiter, but instead it has found another column delimiter. I would
start by carving the file in half, load each to find the bad half. Split
again etc.


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

"Darren Green" <darren.green (AT) reply-to-newsgroup-sqldts (DOT) com> wrote

I have broken the file up, and it works fine when sent in smaller segments.
There is no "offending" row as such.

I read the comments made on the news group posting (link to newsgroup
posting below) which I seem to be getting the same problem. I'm not sure if
any light can be shed on this?

http://groups-beta.google.com/group/...a4dcda52090884

"Ben Rum" <bundyrum75 (AT) yahoo (DOT) com> wrote

Hi, the large file size (48mb) had me in cutting and pasting confusion.. It
was indeed an extra delimeter in the line..

Thanks for your help