Labview exe (2009) does not run automatically when opened

[TanWal]

Hi,

I have built an executable application of my LabView development (run time has been checked in the Additional Installers properties section for Windows Installer). When I click on the build icon (exe file) it does not run the vi automatically, I have to press the arrow key which is highly undesirable given my user group. This is also not my understanding of executable.

Feedback/ assistance would be much appreciated!

[altenbach]

What is your LabVIEW version?

I am a bit confused about your description because you use some strange wording. You only need the run time as additional installer if the target machine does not already have the run time engine installed. This has really nothing to do with the behavior you observe and only has to do with building an installer.

What you are seeing depends on how you built the executable. Are you also building an executable? This needs to happen before you built an installer. Check the VI properties in the source file settings of the startup VI. Make sure you leave "run when opened" checked (this is the default).

Of course if you have an ancient LabVIEW version (pre 8.0?), things are quite a bit different.

Please provide more details. Thanks! (See also)

Message Edited by altenbach on 05-26-2010 11:29 PM

[TanWal]

Yes, I build the executable, then create an installation of my build. I have done the same process in 8.6 with no problems. And as far as I was aware, if you create an installer with run-time it will always over-ride whatever is checked (run on open or not run on open in vi properties). Regardless I did check this option and it did not change anything, the exe still did not run automatically

[altenbach]

Sorry, I did not notice that you mentioned your LabVIEW version in the post title.

---

TanWal wrote:
Yes, I build the executable, then create an installation of my build. I have done the same process in 8.6 with no problems. And as far as I was aware, if you create an installer with run-time it will always over-ride whatever is checked (run on open or not run on open in vi properties). Regardless I did check this option and it did not change anything, the exe still did not run automatically

---

As I said, "run when opened" is NOT an installer feature. "Run when opened" is set when you create an executable. By default, it does NOT use the VI setting, but is enabled. Can you verify your build settings as already mentioned? (It is not clear from your sentence if you are talking about setting the VI property or changing the build specification).

Did you create the project from scratch or did your upgrade the 8.6 project to 2009?

Is there anything special about your application? 

[Tanya_V]

To find the 'Run when opened' option follow these steps:

1. Open your executable's Build Specification

2. Click the Source File Settings category

3. Click the Customize VI Properties button

4. In the execution section, select 'Run when opened' as shown below.

Hope this helps!

[TanWal]

This option was checked as you have suggested, which is why it makes no sense how the program is behaving. Unless someone has set some type of property node in the vi to over-ride this? (I took over project towards end of completion)

[altenbach]

Could there be something in the code itself? For example if there is a stop function somewhere on the diagram, the code might run for a millisecond, then stop. This would look indistinguishable from what you observe.

Maybe it was always there but executed after the main code, but somehow the wire creating the data dependency got deleted and it now executes first.

[TanWal]

I don't think this is the issue because if I set to run on open in the VI properties (not related to build) and click straight on the vi then it does as I would want it to do when I click on the exe

[TanWal]

Found the problem! For some reason 'Enable Debugging' had been checked in the Advanced settings of the build properties. I unchecked this and now all runs automatically as expected 🙂

[chethanchandru]

After  setting run when open setting its works only for single run we required automatically continous Run