Thanks, everybody who wrote in on this. This morning I put the text file
through an intermediary data pump to a holding text file, setting the
properties on the original file to character delimiter (using a character
that does not appear in the file), and setting the transformation to
DTSDestination("Col001") = DTSSource("Col001") + Space(
1321-Len(DTSSource("Col001")) )
where '1321' is the desired record length. Setting the field delimiter to a
non-existent character forced it into recognizing the row delimiter, the
data pump does its thing almost instantaneously, and DTS reads the resulting
file flawlessly.
Many thanks!
JBK
[quoted text, click to view] "Jennifer Kenney" <jkenney@pembrooke.com> wrote in message
news:uqsvEUATFHA.2680@tk2msftngp13.phx.gbl...
> Hi, I'm Jennifer Kenney, I'm mostly SQL/TSQL, but I'm using DTS for
> obvious DTS things, and I've got an issue with DTS respecting the Row
> Delimiters in a text file (source) connection.
>
> The fixed-width text file has a CRLF row delimiter, visible when I read it
> in Word with the view options set to view all, and when I checked to see
> if I could import it into Excel, it read the CRLF just fine BUT!!!
>
> The individual rows are sometimes shorter than they ought to be; the last
> field in the row isn't always present, and my data pump, instead of seeing
> the Row Delimiter and moving the data down to the next row, is filling
> data into the trailing field from the next record, then cutting off record
> 2 after the 30 chars that field allows and starting the next row with
> record 3.
>
> Any advice?
>
> JBK
>