How can I insert a required subVI that is required but Labview won't accept it?

[granthbr]

I am trying to use a VI named Termperature Monitor that was provided in the Labview 7  library included on the CD but it seems to be missing subVIs. I located the subVIs on the cd and attempted to insert them into the block diagram where the question marks are. Despite the fact that the names of the subVIs match what Labview expects, the app won't accept them. Is there a way to force them to accept the subVI that I picked?

[LV_Pro]

Have you installed LabVIEW? and if yes, aren't the example vi's on your harddrive now? How are you "attempting to insert them"? When LabVIEW starts loading a vi and hits a sub-vi that it can't find it will eventually pop up a message with a file search box. If you then navigate to where the vi (with exactly the same name ) resides it should then use that vi. If it, for whatever reason, doesn't match (different connections in particular instance), it should still place it on the diagram, but with broken wires. Alternately you can right click on the blank icon with ?, scoll down to "replace" and navigate to the correct one. This way doesn't require the new vi to have the same name. I'm not sure what happens if the vi you are looking for is on a CD though.

P.M.

[granthbr]

Thank you for the help.
Yes, Labview 7 is installed and so are the examples.
I had not cancelled all of the open file windows yet. I did after I read your message. After I clicked on cancel a couple of times the broken wire did appear and the VI icon was displayed. When I attempt to run the subVI (even though the run arrow is fractured) the error message that is displayed says "The subVI is not executable. You must fix all errors in the subVI before this VI can run.".  Do you have any suggestions on  why the subVI wouldn't be executable?
Thank you again.
Brandon

[LV_Pro]

I'm not sure what you meant by "cancelling the dialog boxes". If you cancel them it doesn't load the vi it was looking for. If a vi has a broken arrow and you hit the run button it should give a list of errors and warnings. If these point towards other vi's then opening them and clicking on their broken arrows should pop up yet another error list with what is wrong at their level. If this is a coding error (ex. "Unbundle By Name: contains unwired or bad terminal") correcting it should fix the broken arrow, and eliminate this sub-vi fom the calling vi's Error list.

P.M.

[tbob]

Double click on the sub-vi that is not executable.  Once opened, click on the broken run arrow.  A dialog box will appear telling you what is wrong with the vi.  You will have to fix each subvi before your main can run.

[granthbr]

It looks as though both of the replies were correct. I was able to open the express vi that was causing the problem. There are errors listed that list a group of VIs that are missing. I think that I just need to locate those VIs and insert them into the block diagram.
Thanks,
Brandon