SubVis on remote machine - which ones are compiled into calling Vi and which are not

[ebloohm]

I have an application in which a compiled exe dynamically loads a SubVi (SubVi-A).

This SubVi then statically calls a SubVi (SubVi-B) which statically calls another SubVi (SubVi-C) ...

All SubVis are part of a source distribution that is copied to the remote machine along with the executable.

If I edit the SubVi-A or SubVi-B on the remote machine, I see those changes when SubVi-A is called.

However, edits to SubVi-C (on the remote machine) are never seen when SubVI-A, B ... are run.

In fact, I can delete SubVi-C from the remote machine without any problem.

However, if I delete SubVi-B, SubVi-A throws an error because it can't find SubVi-B.

I'm thoroughly confused.   Why is SubVi-C compiled into SubVI-B, but SubVi-B is not compiled into SubVi-A?

[crossrulz]

It sounds like you have another copy of SubVI-C floating around that your other VIs are linked to.

[ebloohm]

I've searched that machine, and even rebooted to be sure nothing was in memory ... but I can't find another copy of SubVi-C.

[0utlaw · Accepted solution]

Is SubVI-C also used inside the executable itself?

[ebloohm]

Yup.  It is.  Thank you.