Executable works even if I didn't include all the vis

[Blueyes]

Hi everybody,

I'm facing a weird behaviour building my executable from LabVIEW: I've just realised now I forgot to include some essential VIs in my executable (in the Build Specification properties - Source Files tab). Despite of that, launching the .exe (from my PC where LabVIEW developing environment is installed) I have no problem in getting it to work perfectly!

Possible explanation: in some way missing VIs get called from the executable????

Does someone have a better explanation?

Many Thanks.

[altenbach]

All subVIs in the hierarchy of the startup VI are included automatically. How are you calling the subVIs?

[Blueyes]

I see...

Actually I'm quite new to LabVIEW, been working and playing with it for a couple of month.

So I don't need to put all my VIs in the "Always included" folder, I suppose.

I imagined there should be a simple explanation.

Thanks a lot.

[GoCougs]

The simple explanation is this: If you are calling the subVI's by reference through the VI server they are not considered a "dependency" and therefore are not automatically included in the build of an exe. This is when you would need to place those VIs in "Always Included." When you place a subVI dirtectly on the block diagram then it is included in the dependencies and will be automatically built with the exe.

[altenbach]

Most often, you should always assume that LabVIEW is smart enough to do everything it possibly can automatically. 🙂