Labview runtime - unable to launch VI from compiled .exe

[Slawek]

I have a VI launcher compiled into .exe which dynamically calls uncompiled VIs in Labview runtime.

I have noticed that some VIs do not launch (error: "The VI is not executable") even though they run in development mode. They work when I include them in the Launcher compilation. The uncompiled VIs have datasockets links but thats about it, there is no hardware.

Does it have anything to do with file hierarchy?
How can I determine what causes VI to be not executable in runtime?

[ian_fung]

Where is your (dynamically called) VIs located?

If you happened to use "Default Directory" in the calling VI for calling of your (dynamically called) VIs in development environment, it may not be working once you have your calling VI compiled.

Ex:
[In development environment]
Default directory could be:
C:\Program Files\National Instruments\LabVIEW 6

whereas in installed [Compiled VI], the default directory could be:
C:\Program Files\Gwt_sppd_fctpbda_r001

The VIs will not be called if they are saved in the Default Directory (for Development environment) should calling is required in the installed (executable)calling VI.

Hope you have not confused 😛

For (dynamically called) VIs stored in default directory, you probably can use the at
tached VI to get the correct path. Hope it works for you.

Cheers!
ian

[Irene He]

Hi,
It does have something to do with the file hierachy. If your dynamic
called vis have for example * star besides it's name, even you have no
problem use it in development time, it'll fail in runtime because
LabVIEW runtime not able to compile these unsaved vis or even worse if
you move your dynamic called vis to other places with your launcher,
LabVIEW runtime will not be able to search for the links for you. The
reason that you can use it if you include them in the launcher, your
top level vi, is they are compiled when you build the exe, so all the
file links are fine. So if you don't want to include your dynamic
called vis into the exe file, you may want to build a separate LLB for
the dynamic called vis, including all the subvis being called by these
dynamic
vis. But your software need to have a way to look for these
dynamic vis in development time and runtime, as they maybe at
different relative path.
Hope this help.
Irene He
www.hytekautomation.com
irene_he@hytekautomation.com

wrote in message news:<5065000000080000000FAE0000-1066448259000@exchange.ni.com>...
> I have a VI launcher compiled into .exe which dynamically calls
> uncompiled VIs in Labview runtime.
>
> I have noticed that some VIs do not launch (error: "The VI is not
> executable") even though they run in development mode. They work when
> I include them in the Launcher compilation. The uncompiled VIs have
> datasockets links but thats about it, there is no hardware.
>
> Does it have anything to do with file hierarchy?
> How can I determine what causes VI to be not executable in runtime?