From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Ok Nickels&dimes i got it, only for future readers i solved this case making all this VIs included onto .exe files and they are called by the system exec and each call from a first Vi with a root of case structures called by own booleans... excuse for posting 6 years later!
We took that link offline because we recommend including the VIs in the build. This is because LabVIEW searches through your hard drive and aggregates all functions and subVIs to one location. With just the LabVIEW Run-Time Engine, you must have the same dependencies as the development machine.
If you must do so, you can try the following:
Control the dependency of the subVI by moving it to the desired folder, and then loading the VI into LabVIEW ('Select a VI...' on the functions palette)