excel

[josi_ocroch]

1.  I am using labview 2011 and i would like  to be able to ADD the data to an exising Excel file without disturbing the old data

[GerdW]

Hi josi,

ADD the data to an exising Excel file without disturbing the old data

- You should append new data at the end of the file. There are functions to get/set write position…

- You are NOT handling EXCEL files, you work with plain TEXT files…

Edit: I changed the topic/message subject to reflect your question…

[josi_ocroch]

yes, you  are right..

i have other question, i am using labview 2011 where can i find the "Excel get last row.vi" ? 

[GerdW]

Hi josi,

I don't know.

Where do you got that name from?

In which way is it related with your aim to edit a text file?

[josi_ocroch]

I found the vi in a tutorial from the own national instruments.

I read some data from a ni 5132 many times  and i would like save all this measures in the same file.

[GerdW]

Hi Josi,

in your image above you are NOT handling an EXCEL file! You are working with TEXT files!

The function you named is part of the RGT (Report Generation Toolkit) and is used for Excel automation. Again: you are NOT using Excel files!

[josi_ocroch]

I understood, sorry for any thing.

[NIquist]

Just my two cents here but you're really far better off sticking with text files (.CSV, .TSV, .XML) to store your data.  Those files can be easily opened in Excel (or whatever) for further processing.  The Report Generator Toolkit has been re-factored into LVOOP from its original paradigm of passing references around so it's much better than it used to be but it's still a pain.  We have tons of LabVIEW 8.2 code here that defies updating to newer versions because the RGT VIs are different and a lot of code has to be re-written to accommodate the changes.

Bottom line:  My advice is to always separate your data collection/analysis code from fancy report generators.  Save in simple text formats so your data remains versatile and accessible, then use your tool of choice to create the pretty tables and graphs.  Or better yet, let the people who want the fancy reports generate them so you can get back to solving real problems. 

[Bob_Schor]

---

@NIquist wrote:

Just my two cents here but you're really far better off sticking with text files (.CSV, .TSV, .XML) to store your data.  Those files can be easily opened in Excel (or whatever) for further processing.  The Report Generator Toolkit has been re-factored into LVOOP from its original paradigm of passing references around so it's much better than it used to be but it's still a pain.  We have tons of LabVIEW 8.2 code here that defies updating to newer versions because the RGT VIs are different and a lot of code has to be re-written to accommodate the changes.

---

On the other hand, I really like the new RGT.  We tend to do fairly simple things with it, but we do read and write Excel WorkBooks during the course of our Experiments (we basically use Excel as a "planning document" to select settings for about a hundred parameters that vary from Trial to Trial).  Our WorkBook tends to be "read-mostly" (I'd like to make it Read-Only, but there's some "history" of "the way we used to do it" that I'm trying to overcome ...).

Bob Schor

P.S. -- having said that, the actual data files from the Experiment are XML (for "text-like" stuff) and binary (for sampled data).