Source code works; executable doesn't after using Application Builder LV 6.02

[jberg]

I have a DAQ based program that works just fine, until I try to make a standalone executable. Starting the .exe gives me the error message, "A sub-vi is not executable. The full development version of LabVIEW is required to fix the errors." But there are NO errors running it in the full development version. How do I troubleshoot this? I'm pretty sure I've included all the relevant support files.

[JellyBeans]

Hi jberg,

One thing you can try is to save all of your VIs in a library and then select your top level VI from library when building the executable.
I don't think you need to add support VIs but you need other support file e.g. DLLs etc.

A Rafiq
National Instruments

[jberg]

Thanks!! That worked - I saved all the VIs in a "developer" library, and then built the application. Strange that the Appl Builder docs say you don't have to do this, though...

John Berg

[Kyle_Gupton]

The documentation doesn't explain this because it is not really necessary.
What is necessary is that all of the linkages in your hierarchy of VIs are
correct *before* building the application. I suspect that if you were to
open your VIs in the LabVIEW development environment and then close them,
LabVIEW would start prompting you to save changes in your VIs. This
indicates that the linkage information stored in the VIs does not reflect
the actual state of the VIs on your computer (i.e. LabVIEW had to search to
find a subVI rather than linking to the VI identified by the relative path
stored in the calling VI). If you save these changes and then build the
application, I bet it would work correctly.

Saving things to a new library via the Save Wi
th Options dialog is way of
forcing the linkages to be correct, which is why it solved the problem for
you.

Sincerely,

Kyle Gupton
National Instruments

"jberg" wrote in message
news:506500000005000000981B0000-983677784000@quiq.com...
> Thanks!! That worked - I saved all the VIs in a "developer" library,
> and then built the application. Strange that the Appl Builder docs
> say you don't have to do this, though...
>
> John Berg