How to get the SubVI(the virtual path is under .exe) reference in Run Time System

Question

Hi everyone
The problem is about how to get the SubVI reference in Run Time System, when the SubVI is in .exe after building.
More details:
The top vi calls the SubVI by dynamic way, so the SubVI is included always, and the source object is the application.exe.
After the setup above, the SubVI will be in the application.exe. For example, SubVI's path is ...\application.exe\SubVI.vi
So, how to get SubVI's reference in Run Time System?
 I can not get it when using "open VI reference" with the path ...\application.exe\SubVI.vi in Run Time System.
Actually, I can create a file to include the SubVI, instead of build the SubVI in application.exe , then I can get the reference convenintly. But it is not my favourate way.
Thanks
chenyin
Solved!
Go to Solution.

Answer 1

Here is the problem. Call a dynamic subVI means users could change it but it's also very attractive.
The dynamic call must be used within a user mastered but some parade can avoid problems.
It depends of why you use dynamic calls... => 2 main ways:
- Dynamic call are use to maintain an evolutive  part of the code without acting on the executable => one unique VI distribution maintained by the administrator/developer
- Dynamic call are use to provide a collection of 'external' feature which could be enriched by the administrator/developer. For example, you provide to your customer a set of custom signal filters selectable in the executable.
In the 2 cases, you are only able to assess user skills to know if there is a risk of damage if there is modification.
So, to stay alone master a parade could be to provide dynamic VI without diagram but with the problem of maintenance because no modification in situ and more attention to manage distribution.
An other way is to hide the real distribution to user => call dynamic VI but unnamed it as *.vi but other (a repulsive name as OS system name ) or simply with no extension in order to not  attract user... but it's questionable...
Another method more difficult but safer is to create a test of consistency ahead of your routine (version, user, modification date, ...)