A comma deleted field of string value 38S99555FF0584152 has the alpha
characters stripped out when parsing from csv using LinqToExcel when there is
only one data row in addition to the header row in file.
If there is more than one row in the csv and the field values start with an
alpha character A38S99555FF0584152 then the row one value of 38S99555FF0584152
will read in correctly.
If the value starts with an alpha character B38S99555FF0584152 on a single row
it parses ok.
If I wrap the field in quotes like so ="38S99555FF0584152" it also parses ok.
(as per oledb excel quirk).
I had to give up on LinqToExcel and parse the csv using text and string
manipulation to make this work. The file is an automated csv from a third party.
In an xslx no problem. LinqToExcel is great utility but in this scenario I was
forced to admit defeat.
I'm sure this is an oledb problem but I can send the code snippets and the csv
file if you would like to see this in action.
cheers
Steve
Original issue reported on code.google.com by chalkste...@gmail.com on 21 Nov 2012 at 4:07
Original issue reported on code.google.com by
chalkste...@gmail.com
on 21 Nov 2012 at 4:07