When your Project is open, you can see some of the Dependencies, other VIs associated with the VIs listed in your Project. This can include VIs that are in the Physical folder containing the Project but not in a Project Virtual folder, VIs in libraries, including .llbs, vi.lib, and user.lib, .dll files (from NI and others) referenced by items in the Project, and possibly other things. These are items that it finds on your current machine, and that you would need if you moved your code to another computer.
When you load one of the VIs in your Project into memory, it will do a further search to locate all of the functions that it uses, raising an Error condition if one is not found (sometimes due to a missing Driver, for example). A trick that I like to use during Development is to create a "Tree" VI that contains a copy of every VI in my Project. If I open the Tree, and any VI makes a call on a "missing function", I will have a Broken Arrow, and can use the Error reporting to find the Missing Link.
Bob Schor
