Application splitted into two .exe

[Mivil]

Ben:

I tryed 1 month ago but because I'm running on a run-time licence, I don't know how to package my user VI. I got a lot of missing VI because my user VI is using advanced math function didn't included on my main application!

Do you have a solution to be sure that my user VI will come with all it's subVI and will be functionnal on a LV run-time?

Thanks, Jean-Marc

[Ben]

The user has to provide the sub-VIs (otherwise like selling a car with no engine).

You can check the error cluster after attempting to open the target VI to ensure it opened correctly.

another approach could use LVOOP and let your users provide child classes to over-ride the parent call. LVOOP classs transport nicely as their own libraries.

Ben 

[Mivil]

Does the LV dev. version must be the same (main application and client VI) or the called VI can be create with a different version?

[Ben]

Last I checked they can differ but you should check yourself and not trust me.

Ben

[dan_u]

---

@Mivil wrote:

Does the LV dev. version must be the same (main application and client VI) or the called VI can be create with a different version?

---

There's several potential configurations here (assuming your part is compiled into an exe):

1) Only run-time engine available on target machine
In this case the VI would have to run within the exe. This only works if the LV version used to create the VI is the same as the LV version that was used to create the exe.

2) LabVIEW development system available on target machine

In this case you can also run the VI in LV instead of the compiled exe. This works with different versions of LV. LV development system needs to be running when you try to open and run a VI in it.