I am trying to use DTS to import a text file with no field delimiter using
fixed length fields. Imporing rows with less than the max possible row
length ignore the row delimiter and data from multiple fields end up in the
same record. I've seen similar issue in the KB but not this exactly. Is it
possible to import the data using DTS without padding each row to the max
length? Seems to be a bug with DTS because the ROW DELIMITER is there and
being ignored. Another quesiton, does SQL 2005 address this issue?

I have not seen this error before, but you may be able to address this issue
by using a multi-phase data pump. This gives you much more control over how
DTS is handling your data at each stage of the transform. You can instruct
DTS to "allow" the row instead of failing it based on a wide variety of
conditions. It sounds like your source file has some "optional" fields in
it which are not padded with whitespace--is this something you can fix at
another level?
John Glass


Follow this link for more information:
http://msdn.microsoft.com/library/de...mtsk1_2yux.asp


"The Kat" <TheKat (AT) discussions (DOT) microsoft.com> wrote

DTS is not failing rows that are not padded with spaces so I am not sure the
multi-phase recommendation will fix the issue. DTS is just doing it wrong by
concantenating (combining) the shorter row with fields from the next row.

"John" wrote: