LabVIEW
Error Saving File with MS Office Report Express VI
@Bob_Schor wrote:
Here are some comments and suggestions (sort of "How I Do It" and things you might try):
- To be honest, I'm not 100% certain I understand the difference (to Excel) of an Excel Template (.xltx) and an Excel Spreadsheet (.xlsx). I do not use Excel Templates -- if I want to read an Excel Spreadsheet (.xlsx) file, getting data from rows and columns, I wire the .xlsx file into the New/Create Report "Template" input. If I'm "updating" a file (both reading and writing the same file), I need to wire the Path to the Save Report function, as well. It has always worked for me. You might try using a Spreadsheet File as your Input file and see if that makes any difference.
The express VI "MS Office Report" requires that the template format be .xltx.
@Bob_Schor wrote:
- When you build an Executable, you get a Data folder placed at the same level as your .EXE. I use this as the starting location for any Data Files I need to read or write in my Application. Here's a Snippet of code that I use to find the path to the Data Folder in my Executable:
The Green folder is an OpenG utility that creates the Folder if it is not present (you probably don't need this, I'm just being Super-Careful) (I think that such a function, to create a possibly-nested directory, may have been included in LabVIEW 2019 -- yes, there's now Create File and Containing Folders, and Create Directory Recursive).
- The trick to making this work is to also have a Data Folder as a "top-level Folder" in your Project Folder. When you are in Development Mode, the Application Directory is the Project Folder, and when you are in Execution Mode, it is the folder you specify on the first page of the Build Spec (I like to use the Public Documents folder as the place LabVIEW puts its LabVIEW Builds folder, as all the Users can access it, but it is not, by default, "visible").
I tried saving the report to the "Data" folder within the application directory and experienced the same fatal crash as before.
It's not 64 bit Windows that's the problem, it's 64 bit Office, which is a fairly recent change (I had issues with 2016 as well). My dev machine had 2013 and the lab had 2016, and it wouldn't work.
Regarding debugging, you can see the BD of a built executable if you follow these steps:
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000PAiTSAW
Good to know.
For future Googler's of this problem, Office 365 now installs 64-bit Office by default. See this article for info on how to install it as 32 bit:
By the way, here's another thread where the author seems to be able to create files, but has errors upon saving them: https://forums.ni.com/t5/LabVIEW/Save-Report-to-File-Report-Generation-Toolkit-isn-t-actually/m-p/38...
He never replied so I don't know how it turned out.
Also, as a further resource of people with general issues with the Report Generation Toolkit, see this knowledgebase article: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019N7CSAU&l=en-US
OP, that third link may help you out if you can get remote debugging working. Maybe not, but worth a try. That's what fixed my original RGT problems.
