how can I tell which subVI changed?

[MattI]

Sometimes I open a VI, and upon opening (i.e., before I do anything), it says the VI has changed.
If I use File/Revert, it still opens up that way.
In such cases, LabVIEW also asks if I want to save changes when I close it.
When I look at the changes using File/VI Properties... under Category: General, by clicking on the "Current Changes" button, it says:
VI recompiled
SubVI call(s) modified.

I understand that this means something changed in a subVI, but I don't always know what changes prompted this, and I would like to be able to investigate further.
What can I do to determine which subVI changed, so that I can investigate if it might adversely impact my VI?

[maymaythar]

Sometimes, you duplicate your subvi and save in several location. Thats why you faced this problem. One way to solve is use library to save all your sub vi including your main vi.

[Greg_McKaskle2]

> When I look at the changes using File/VI Properties... under Category:
> General, by clicking on the "Current Changes" button, it says:
> VI recompiled
> SubVI call(s) modified.
>
> I understand that this means something changed in a subVI, but I don't
> always know what changes prompted this, and I would like to be able to
> investigate further.

One easy way to investigate it is to click on ring at the top of the
Explain Changes dialog. This will list the other VIs with changes.

One of these is the subVI, and selecting it from the ring will list its
changes. It is likely a version or platform change.

Greg McKaskle

[MattI]

I need to use a directory structure, not a .llb, because I have literally 1000s of VIs that I have created, and a .llb-type organization is far too "flat". I could use many .llbs, but it gets me back to the same situation.

[MattI]

This is true only in the rare situation where the change was made in the same session. In such a case, I am likely to remember what I changed anyway! It is when I open a VI & it says that a subVI has changed that I would like to know which subVI(s) changed, so that I can investigate its impact on the execution of my VI.