I've wrote an installer using the Application Builder to install the Run-Time Engine that allows any computer without LabVIEW to run a .exe program. The installer runs and installs the run-item engine and then also a .exe VI. When it is done installing, the .exe VI opens automatically. An error pops up when the .exe opens up and says "Error 1 occurred at Write to Text File". If the user clicks out of the error he can run the program no problem, it converts file formats in a .lvm file. It automatically generates a new file name and saves the file to the same directory but with a different name. Why did this only happen when first opening up? Does the program try to run when it automatically opens up? Is there a residual file path left in the program that trys to run first before the user puts his own file path into the program? I'm semi new to labVIEW (a few months) and just can't see anything that would create this error at the start of the program. Thank you

Hi Scott, well, you could mock up a small VI and turn on Highlight-Debugging to test your idea! THINK DATAFLOW!!! How should a boolean input WAIT for user action? It will be read according to DATAFLOW! What about that small pseudocode: REPEAT wait(50ms) UNTIL button pressed Or what about an event structure waiting for user action?

LabVIEW

Error 1 occurred at Write to Text File - Installer with Application Builder

Solved!

Author

Thank you I figured it out. I placed it in a while loop that constantly runs every .25 seconds and then a case statement inside of that only allows the code to run when the user clicks run.

Message 11 of 11

(679 Views)

LabVIEW

Error 1 occurred at Write to Text File - Installer with Application Builder

Re: Error 1 occurred at Write to Text File - Installer with Application Builder