LabVIEW
Save a File to Disk using Build Path in Executable
@Sam_Rudneff wrote:
If you're saving a file to a C:\ path, try to run your executable as administrator. Maybe your program just don't have enough privileges to save file at this location.
That's one of the main reasons I tend to always save my data to the Public Documents.
The openg variant of build path makes no difference here. (The only difference is that it accepts arrays, see See here, fo example ).
Are you testing on a different or on the same computer?
If different, does it contain the same version of office? Does C:\data exist? Is the app allowed to write to it? Do you get any errors?
As others already said, writing to the root (or close to) the root of the drive is not recommended.
LabVIEW 2011 is not supported in windows 10, so there could be other issues.
@DeOdderKeith wrote:
I was sent this article which seemed to allow the application to run properly.
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019O6PSAU&l=en-US
Yep, been there. Since the Report Generation Toolkit dynamically loads the object that is needed, the app builder does not know it needs to include the Excel class. So you have to add that library/class to your project and then "Always Include" it in your application.
