Dependant VI's that are not really in the top VI.

[jperch]

I am trying to build a project into an executable. When I add my top level VI, the dependancies folder gets filled with all the sub-VI's. The problem is that several of these VI's are showing as having been moved or deleted from the disk. When I search for them in the top level VI, they are not really there.

Can anyone tell me how to remove these from the project?

Joe

[JÞB]

Select>>Right-click>>Remove from Project  Does not work on auto-populating folders stop auto-populating may be needed first

[jperch]

Jeff,

Thanks for the tip. But, I am referring to VI's that are in the dependencies folder. these are auto populated when you add the top level VI. You cannot right click and remove (I tried).

Basically, when you add the top level VI, the project checks to see what sub VI's the top level calls and automagically populates them into the dependencies folder.

In my case, it is somehow finding sub VI's in the top VI that are not really there. They used to be. But I have removed them. I have tried using the find untility in the VI hierarcy view as well as the find utility under the Edit menu.

Here is a picture:

[Puneet_K]

Hi Joseph,

You need to find those VI, where you are using it in the application. If you dont need these VIs, delete from code.

Save your project, it should disappear from the project.

[jperch]

Puneet,

I have done that. The VI's that are flagged as missing or renamed have all been deleted from the top level VI. That is what I mean by "The VI doesn't really exist". This is what concerns me.

I went ahead and performed the build. That seemed to proceed okay. It is as if the project doesn't really need them because they are not really called or used in any way. It is just the display that seems to be confused.

I guess my root question is now, can I safely ignore this and move on or will this bite me in the end?

Joe

[dkfire · Accepted solution]

Try to right.click on the vi's and select Find -> Callers. This will give direct you to the vi's that are using the missing files as sub-vi's.

There might be some other vi's in your project that is using the missing vi's.

[jperch]

THAT'S IT!!!

dkfire, you solved it! It turns out one of the other sub VI's was calling the missing ones. However, the calls were within the disabled frame of a diagram disable structure. That is why it didn't generate any errors. I am guessing they didn't show up in any search tool or hierarchy because either they were disabled or because they weren't found.

At anyrate, thank you very much. I feel much better now. That was driving me crazy.

Joe