Help with Dynamically call VIs

[crossrulz]

You can actually simply things a little bit more.  The Build Path knows how to handle "..\", which will strip away a level of the path.  So I will often use something like "..\subVI.vi" with the Build Path and Current VI's Path to build the path to a VI I need to call.

[Hooovahh]

I'd agree with what others are suggesting.  Use a static VI reference and LabVIEW will know it is a requirement and include it as a dependency.  The only thing I'd add is I usually use the VI name instead of the VI path, but either way will work fine in an EXE.  If your VI is unsaved then obviously the file path doesn't exist and that won't work but VI name will.  Here is an example I posted a while ago.  If you build that into an EXE it will work fine without needing to set the always include.