"Add a dynamically VI" in Application Builder to prevent Error 1003 is no solution for a steadily rising amount of SubVIs.

[Michael Winkler]

My VI calls SubVIs (all with the same connections) in a loop with one 'call by reference'. It works great in the VI but when I build an Application I receive Error 1003. After that I read in the KnowledgeBase when I build the Application I must add dynamically all the SubVIs I call by reference. Works fine at the moment but the amount of the SubVIs is rising steadily (approximately 10 per week) and there are many users all over the world of this application. So it is practically impossible and very uncomfortable to build a new application everytime the amount of SubVIs rises. There must be another solution maybe some kind of initialization, adding
the paths of the dynamic called SubVIs programmatically???

[Dennis_Knutson]

You do not have to include all the dynamically called subVIs in your build. If you look at the shipping example called Plug In Example, the dynamically called VsubIs are in a subfolder called plugins. In this example, the paths to the subVIs are created based on what files are present and which have the correct type specifier. The high level VI can be built into an executable. The plugins folder could also be included with one or two subVIs but once installed, new subVIs can be distributed separately and just put into the folder. The only trick is to make sure that the path to the plugins folder is correctly obtained whether the VI is run in development mode or as an exe.

[Michael Winkler]

Where can I find the shipping example called Plug In Example? If it's too difficult to find please send it to me via email (michael.winkler@lvf.liebherr.com).

[Michael Winkler]

I found the Plug in Example and changed my source code. Now I get error code 1 in the application (Error when open reference; an output parameter is invalid). Is it possible that it has something to do with the typ-definition of my input and output parameters in the SubVIs. Maybe they must be strict-typed??? I am using LabVIEW 7.0 Base Edition. Is that a problem???

[Michael Winkler]

It works perfect!!! I have forgotten to add a second SubVI to the Application. The SubVI that I use strict typed at "open reference" is not enough.