comment on

You got me thinking. If I take out the getline and put the parse in the loop and add your error_diag(),

use strict;
use warnings;
use Text::CSV_XS;

my $tr_csv = Text::CSV_XS->new({ binary => 1, eol => $/ });
open(my $tr,"<",'file.csv') or die "Failure opening ERS data file: $!"
+;
while (my $row = <$tr>) {
    $tr_csv->parse($row);
    print $tr_csv->error_diag(),"\n";
}
[download]

I can get some errors.

2032EIF - CR char inside unquoted, not part of EOL436
2032EIF - CR char inside unquoted, not part of EOL435
2032EIF - CR char inside unquoted, not part of EOL433
2032EIF - CR char inside unquoted, not part of EOL425
2032EIF - CR char inside unquoted, not part of EOL425
[download]

I guess that means it's worse than just having two extra characters at the beginning.

non-Perl: read my music blog be my fan at Reverbnation bump me at the Sixty-One

In reply to Re^2: Parsing MS SQL CSV export with Text::CSV_XS by andyford
in thread Parsing MS SQL CSV export with Text::CSV_XS by andyford

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks