Leaderboard

After many frustrating experiences with patched together CSV parsers (admittedly of my own creation), I've finally broken down and developed a CSV file parser that follows the RFC-4180 format: http://tools.ietf.org/html/rfc4180 That is to take into account double quotes and commas inside double quotes and multiple-line entries. This is essential if you plan on storing user-input text data or storing numbers that may have a comma as a decimal point. From what I can tell, this is the same format that Open Office, Libre Office and Microsoft Excel use for their CSV file export. Therefore, using this format, you can export from LabVIEW to CSV, open it in Excel, make changes, export from Excel to CSV then import it back to LabVIEW without everything being broken by a missing double quotation mark or an extra comma. Attached is the VI to parse a CSV formatted string to a 2D array of strings for LV 2013, 2012 and 8.6. I've also attached an example CSV file (inside Test1.zip) exported from LibreOffice to demonstrate some of the tricky cases that most CSV parsers can't handle. Please give it a try and let me know your thoughts. Update: I've posted the finished library to the Code Repository Database & File IO catagory here http://lavag.org/files/file/239-robust-csv/

Dear LabVIEW Expert, Have you always asked yourself how to effectively and remotely push updates to the client? How to license software and protect intellectual property? And how to manage thousands of licenses and applications? The answer: BLT for LabVIEW. We worked hard to provide a powerful management software that will give you the tools to protect and distribute your LabVIEW programs, for internal or commercial use. As a LabVIEW developer, your feedback is really important to us since our toolkit is mainly designed for your needs. That's why we would like to offer you a free version with all the features included, so you can test BLT and see how it improves your daily productivity. Please refer to www.BLTforLabVIEW.com (http://bltforlabview.com) or watch the video for more information. Matthias Baudot Principal Software Architect STUDIO BODs INC. contact@studiobods.com

Just ran into this one personally. Not sure what the offending VI is but replacing the one in the vi.lib with the one you posted fixed it. Can't wait until SP1.