Reading .csv file with semicolon delimiter

[rmil565]

Hi,

I am trying to read the attatched .csv file (attached) which is formated with the ";" delimiter.

When I read the file using the read delimited spreadsheet VI I get an output array with a new line created between each row of data.

Does anyone know why this new line is been created and how I might be able to read the file?

(I am able to resave the file to comma delimieted format using excel, and read successfully however my application is such that I need to read the original semicolon delimiter format)

Thanks,

Richard

[mikeporter]

I'm not sure if I understand you. A linefeed is what makes a row a row. Do you means there is a extra line feed? Can you show a sample?

Mike...

[rmil565]

Heres the read output of the semicolon delimiter defined file:

 

 Heres what I want:

[rmil565]

Please see message above

[rolfk]

The file uses the DOS end of line indicator <cr><lf>. When reading the file into LabVIEW you should enable the option "convert EOL" on the read operation to let LabVIEW convert the platform specific EOL indicator into its own native <LF> EOL indicator.

[PalanivelThiruvenkadam]

I changed your file to CSV Extension, It works fine.

whats the Need to have a csv file with .xls exten?

[mikeporter]

I think the intent was to have a file that excel can open as well. Excel can open certain types of delimited files automatically.

As Rolf says, the issue reading the file into LabVIEW is with the EOL delimiter. Any time you see "extra" lines being inserted, be thinking EOL delimiter. Just to keep things totally confused, Windows uses a single linefeed as a delimiter, however Notepad -- which is part of Windows -- expects both a carriage return and a linefeed. If it sees a single linefeed, it ignores it and runs everything into one long string.

Mike...

[rolfk]

A slight correction:

Windows still generally uses <cr><lf> like DOS for ASCI text files. MacOS Classic used a <cr> and most Unix variants usually <lf>. LabVIEW as a multiplatform application had to standardize on one of them for internal use and decided for the <lf>, but the text file read and write functions have an automatic EOL conversion option. 

[rmil565]

Thanks for the help!

After doing some more research into the file type the csv file i realised is coded using unicode.

Simialr to the problem here: http://forums.ni.com/t5/LabVIEW/Labview-not-reading-csv-file-properly/td-p/2855176

I was able to use the same solution