labview 8 build executable question

helpo · ‎02-08-2007

I created an executable in Labview 8 and everything seemed great. I set it so it didn't run when opened and it worked correctly. Then I went back and made some changes and disabled debugging and now the executable runs when opened irregardless of the fact that run when opened is not checked. I double checked everything and it seems that disabling debugging is what causes this. Is this supposed to work this way? It doesn't make any sense to me but I can work around it for now.

Riconquistiamola · ‎02-09-2007

Hi helpo,

An executable should not run when opened if built in LabVIEW 8.0. What changes were made? Did you edit the VI Settings at all?

It may be a good idea to remove that Build Specification and start from scratch, or even try to rebuild a completely separate project to see if this behaviour spans App Builder..

Cheers.

| Michael K | Project Manager | LabVIEW R&D | National Instruments |

helpo · ‎02-09-2007

Thanks,
I actually figured out a setting that causes it to run but there is still a weird bug that causes it to not run when you have everything set to run but you have debugging disabled. I don't know what is going on with that. I have it working the way I want it to now.

Riconquistiamola · ‎02-12-2007

Hi helpo,

Could you give me steps for reproducing the bug? If there's something wrong with the 8.0 App Builder we'd like to know.

Cheers.

| Michael K | Project Manager | LabVIEW R&D | National Instruments |

ycheng100 · ‎02-28-2007

I met a similar problem with Labview 8.2 when I tried to build an executable from a VI that's written in labview 6.1. I'd like it NOT to run when opened but no matter what I set, it always runs when opened. What's more interesting is:
If I try to view the build spec after I just open the project, I would see the following (Run When Opened value False)

Next to click a category such as "Preview"

Then I will get this if I go back to the source file settings (Run When Opened value True)

I'd like to know why.

Message Edited by ycheng100 on 02-28-2007 05:03 PM

Riconquistiamola · ‎03-01-2007

Hi ycheng,

This is a known problem with LabVIEW 8.2. This was reported to R&D (# 42AA34OZ) for further investigation. A possible workaround is to specify the VI settings you want in the development environment.Thanks for the feedback!

Cheers.
Michael K. | Applications Engineer | National Instruments

| Michael K | Project Manager | LabVIEW R&D | National Instruments |

ycheng100 · ‎03-02-2007

Hi Michael,

Thank you for your reply. Actually I always set the 'run when opened' to false in the VI settings, but the source file setting in the build spec will overide it and always set it to true. So I don't think this workaround will work.

Yuan

@Riconquistiamola wrote:
Hi ycheng,

This is a known problem with LabVIEW 8.2. This was reported to R&D (# 42AA34OZ) for further investigation. A possible workaround is to specify the VI settings you want in the development environment.Thanks for the feedback!

Cheers.
Michael K. | Applications Engineer | National Instruments

Riconquistiamola · ‎03-05-2007

Hi Yuan,

I have found a very simple way to override the Run When Opened setting is to cause the program to stop with the default values causing the stop. For example, create a boolean wired to a case structure which incorporates the entire top-level VI. Set the boolean to false, where the false case contains nothing and kills the program immediately. The executable will open and stop and appear as if it had never been run in the first place. Then, simply change the boolean to true to run the program normally.

Cheers.

| Michael K | Project Manager | LabVIEW R&D | National Instruments |

ycheng100 · ‎03-05-2007

Hi Michael,

Thank you for your reply. I think that will work. However, I'll need to add that to every top-level VI I'll build an EXE from with Labview 8.2 and there're a lot of them. I hope I can get some patch to update the application builder of labview 8.2 instead so that I don't have to modify all the old functioning VIs.

Have a great day!
Yuan

@Riconquistiamola wrote:
Hi Yuan,

I have found a very simple way to override the Run When Opened setting is to cause the program to stop with the default values causing the stop. For example, create a boolean wired to a case structure which incorporates the entire top-level VI. Set the boolean to false, where the false case contains nothing and kills the program immediately. The executable will open and stop and appear as if it had never been run in the first place. Then, simply change the boolean to true to run the program normally.

Cheers.

pranav · ‎09-12-2007

Hello,

I am also facing similar problem like Ycheng. I am having Labview 8.2 Dev Suite and building EXE using 'build executable' menu to deploy it on other PC. I also set "Run when open" property unchecked(false) in both VI setting and in source file settings. Still when I run EXE, it starts running when double clicked.

Solution suggested by Michael is good, but I would like to know ( as Ycheng also suggested) whether NI has released a patch with correction ? Recently I have got some update CDs from NI as our version is still under one year free update agrrement. Does it contains above things ?

regards

Pranav

LabVIEW