The reference to the configured VI.
The VI you use to configure Static VI Reference should be accessible and under the same target; in other words, if the VI belongs to a component different from that of the owning component of the Static VI Reference node's parent VI, it should be an exported VI. If not, the reference produces a compile-time error.
Specify whether the Static VI Reference is strictly typed on the Item tab.
To change the output of this node to a strictly typed VI reference, select Strictly Typed Reference on the Item tab. The strictly typed VI reference identifies the VI you are calling. You can create a strictly typed VI reference only from a VI, not from a non-VI file such as a control.
Use a strictly typed VI reference if you want to call the referenced VI with Call by Reference or Start Asynchronous Call. When you create a strictly typed VI reference, you can wire VI reference to the Run VI node.
The application loads the referenced VI into memory when you load the top-level VI. When Static VI Reference outputs a strictly typed VI reference, the application reserves the referenced VI as long as the top-level VI is running. The application closes this reference when the top-level VI is no longer in memory. You do not have to explicitly close the reference this node returns.
The compiler does not check whether the referenced VI can compile. If the referenced VI is broken, the VI containing the Static VI Reference breaks due to an error in dependency. If you execute the Open VI Reference node that references the broken VI, you receive an error.
If you want the compiler to check for a broken referenced VI before you run the top-level VI, use the referenced VI directly in the top-level VI instead of using Static VI Reference.
A strictly typed static VI reference also reserves any subVIs when a top-level VI is reserved, therefore you get a runtime error if you attempt to run the referenced VI using the RunVI node and any of the reserved VIs have a caller that is already running.