Save Report to Fil.vi crashes when built as executable

[Bob_Schor]

Sorry, you probably said all of these things in your earlier posts, but I missed some of the details.  To summarize my (updated) understanding of your problem:

• You have a LabVIEW Program that saves data to Excel using the Report Generation Toolkit.  It works on the Development machine, both in LabVIEW, and when built as an Executable and run on the Development Machine.
• You try to run the Executable, built on the Development Machine, on a Target Machine.  It "tries to write the file to some crazy location".

Questions:

• Do you know where it is trying to write?  Can you, for example, put an Indicator on your Front Panel to hold the full Path to the File Parameter wired to "Save Report to File"?  This might be a useful clue for us to have.  [Be sure to make the indicator wide and several lines tall so that the entire path is visible].
• Are the Operating Systems on both Development and Target computers the same, both in Version and in "bittedness" (i.e. both w32 or x64)?
• Are the versions of Excel 2016 on both machines the same bittedness?  [Is there a better word for ("32 or 64-bit"?].
• Have you installed the proper version of the LabVIEW RunTime Engine on the Target machine?

Bob Schor

[StevenHunter]

Dev - Win10, LV18-32bit, Excel2016

Target - Win7, LV18 Runtime, Excel2016

As the code shows, I am reading from the C:\Timing\Files directory.

As the error screenshot shows, it opens the file, then crashes when it tries to write to \Device\Harddisk1\DR29. This also deletes the file from the C:\Timing\Files directory. 

[Bob_Schor]

---

@StevenHunter wrote:

As the code shows, I am reading from the C:\Timing\Files directory.

As the error screenshot shows, it opens the file, then crashes when it tries to write to \Device\Harddisk1\DR29. This also deletes the file from the C:\Timing\Files directory. 

---

I'm confused.  The only code I've seen is in the Zip file you posted April 4, which has a single VI, Save Excel File.  It writes to the C:\Timing\Files folder (but doesn't check if such a Folder exists).  I'm also puzzled by the reference to \Device\Harddisk1\DR29, which doesn't appear anywhere in the (very small) program.  Oh, well.  I haven't been able to duplicate the error, but I'm probably not doing it wrong right.

Bob Schor

Bob Schor

[StevenHunter]

I also tried using the Microsoft Office Report Express VI, but that generates Error #-41110, but at least it does not crash the program.

[Bob_Schor]

Why don't you post your code again?  As I tried to tell you in my last Post, the code I saw seemed "wrong" and curiously incomplete -- it's almost as hard to debug "code that seems to be the wrong code" as "code that isn't posted".

Bob Schor