VIs from LabView libraries not found in .exe built with Application Builder

[BVSmith]

I have added VIs that are called by reference to the dynamic vi list in the App Builder, but some of them fail to run because of sub VIs that aren't found at runtime.
These sub VIs are from the standard LabView libraries. For example: "Open/Create/Replace file.vi", "Write Key (I32).vi", "Open File+.vi" and "Read File+ (string).vi". Also, a typedef "ADC.flx.ctl" can't be found(from the Motion CustomControls library).
Even if I have those VIs open when I compile all of my VIs (using Ctrl-Shift-Run), they can't be found when I run the executable.

[dan bookwalter]

Make sure the user has rights in the directory that contains the vi's etc...

Dan

[BVSmith]

Yes, I have administrator rights so I know I have access to everything.
I find it strange, however, that it complains at runtime that it can't find things that should have been compiled in at compile time - especially a typedef.

But then, I don't know how LabView does these things.

That would also imply that the target machine would have to have the LabView/vi.lib/... libraries installed. Or are those part of the Runtime engine too?

[Philip_Courtois]

Are you running the executable on the development machine? If not, make sure that all the required drivers are installed on the target machine (i.e. NI-MOTION etc.).

The version of the LabVIEW Runtime Engine also has to be the same as the LabVIEW development version.

Under �Application Builder >> Target >> Build Options� make sure to choose �Single target file...�. This way all sub VIs will be compiled into the executable.

In LabVIEW 7.1 you can choose to �Disconnect type definitions�� under the �Application Settings� in Application Builder. Does it help to remove the checkmark?


Best regards,
Philip C.
Applications Engineer
National Instruments
www.ni.com/ask

[BVSmith]

Yes, I am running the executable on the development machine.

I first tried building one executable file but when it couldn't find those VIs I switched to building a small executable and separate .llb. That didn't help.

Lastly, I added the missing LabView library VIs to the "dynamic vi" list, and it compiles and runs now.

[BVSmith]

My mistake. I had some sub-sub call-by-reference VIs that were using those LabView library VIs.
After adding those to the dynamic VI list I didn't need to have the LabView VIs in the list anymore.
Thanks for the help.