Link to home
Start Free TrialLog in
Avatar of Burzhuin
Burzhuin

asked on

Flat Text File Format

I got a new Vendor and FTP the flat text file. However for some reason  <carriage return> and <linefeed> does not work and instead of structured data (seven fields per row I got one string. In my package the row terminator is set to {CR}{LF} but seems cannot find it in the text. Did anybody have this problem before? Any suggestions? Thank you.
Avatar of Anthony Perkins
Anthony Perkins
Flag of United States of America image

Are you show the row delimiter is CrLf?  Perhaps it is just Lf.  You can confirm this with a Hex editor otherwise you can post a sample here and we can verify for you.
Avatar of Burzhuin
Burzhuin

ASKER

I confirmed it and it is CrLf.
Then I am afraid I have no idea what could be going on given all the information you have provided.

Good luck.
ASKER CERTIFIED SOLUTION
Avatar of AlexPace
AlexPace
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
How about the field terminator, what is it set for? Also can you attach a data sample?
@AlexPace, ASCII mode normally does line-ending translations, BINARY mode does not.  In addition, it does it going both ways so even if it gets translated when uploaded, it will be re-translated when downloaded so it will look like nothing was changed on the server when it was.
@DaveBaldwin, yes that's why I suggested it.  It is possible that the new host is not a windows box so using ASCII mode will "fix" the line endings as far as SQL Server is concerned.
@AlexPace, good then, I wasn't sure.  Looks the poster agrees with you.