Dynamically load VIs using List Folder and Open VI Reference

[AttilaZ]

Hi guys,

I use the following structure to load VIs dynamically:

It works perfectly when I’m in development mode, but I do not know how to build the executable from this structure, because the “List folder.vi” does not work. Should I save the VIs in a separate folder or in an llb and load them from there or is it possible to bundle all the VIs in an exe and call them dynamically from there somehow?
 
Ideally at the end I would like to have only one exe with all the VIs bundled in it, but I don’t know if it can be done or not.

Thanks

Attila

[smercurio_fc]

What does the "vi path" control refer to. I'm guessing your problem is a variant of this: Why Does My Executable Not Work When Using the Current VI's Path Constant?

[Wiebe@CARYA]

Probably because the VI Path you use as input isn't the same, because now
the VI is in the executable.

Vi path of VI foo.vi will be c:\test\foo.vi when run in the development
environment, but it will be c:\test\foo.exe\foo.vi when called in an
executable at the same location.

Regards,

Wiebe.

[AttilaZ]

Guys,

I’m using different paths depending on the execution mode. This is not the issue. The problem is the “List Folder.vi”. I cannot list the files within the exe. Is there any other method I could use?

[tst]

Accessing VIs Inside of a LabVIEW Executable or DLL in LabVIEW 8.2 and Later [link removed; article no longer available].