Ok first where are the settings for throwing away incomplete rows....dont member that one from training classeskcbland wrote:You have an entry line in the file is what you are saying. You have an extra carriage return/line feed somewhere. Either the data has it embedded in it, or the concatenation is somehow introducing it.
You can configure the sequential stage to throw away incomplete rows, or you can configure the sequential stage to complete incomplete rows where by you have to introduce a transformer constraint to throw them away. This at least moves you forward. You still have to find out which file is bad. You can look at the link statistics from the job that produces the individual files to get the row count, then go to the produced file and verify which file is wrong. If one of them is wrong, you have just provided that concatentation is not the problem, but its the data. If the files match the link statistics, then the concatenation of the files is the issue (sooo very not likely).
![Smile :)](./images/smilies/icon_smile.gif)
second u are saying count the number of rows that are actualy in the files vers what DS says it outputs are the same.
what bothers me about this is that if i load the files by them selves they do not error. if there was an extra character in the file then i would imagin that it would not load at that point eather....this is what is confusing me about your theries.......
Jim