Create an XML file that could be well read with MS EXCEL

[stevensung]

I have created an xml file in LabVIEW with data from a tab that has multiple pages. What I would like to have is to open this file in MS EXCEL and have one dedicated worksheet for contents in each tab page. It seems like that particular information is not carried out in the xml file which was created with LabVIEW schema. Therefore when trying to open it in EXCEL I only get one single row of data (though that has so many of columns, one for each data entry). I am attaching my source code and hopefully one could help me to find the solution.

Thanks,

PS: In the attachment, the file VI_FP.png is a snapshot of the main VI front panel. Two VI snippets could show the main function of this work. And the .xml file is what is been created with this work. 

[RTSLVU]

I just have to ask why you are creating an XML file if you want something Excel can read and import?

[stevensung]

I try to avoid using the report generation toolkit which has the known version compatibility issue. 

[natasftw]

You'll likely start here: https://en.wikipedia.org/wiki/Office_Open_XML

It'll be hard to help you much when you're sending snapshots of things instead of things that can be worked with

[Rochellingham]

---

@stevensung wrote:

I try to avoid using the report generation toolkit which has the known version compatibility issue. 

---

Have you tried XLR8?

[JÞB]

You are not going to be happy with your code.  The LabVIEW xml routines rely in DOMUserDefRef.dll this dll is actually very useful for maniplulating DOM (Document Object Model) components but it is very slow single threaded and non reentrant.

So here I get to give a shout out to JKI for the "Easy XML Toolkit for LabVIEW" its open source and free plus it works.

[Bob_Schor]

---

@JÞB wrote:

So here I get to give a shout out to JKI for the "Easy XML Toolkit for LabVIEW" its open source and free plus it works.

---

... and I can mention NI GXML (also available, along with Easy XML, on the LabVIEW Tools Network) that I use.  I appreciate that this comes in Source form, so I've taken the liberty of modifying it so I can do things such as write out XML files "entry-by-entry", rather than requiring the entire XML file to be written "all at once" (which means all the data needs to be in memory).

Bob Schor