Occasionally TestStand forgets where its VIs are and I have to waste a lot of time reminding it. Here's what I'm trying to avoid:
1. Occasionally I will analyze my sequence and TestStand shows in its Analysis Results pane hundreds of unexpected errors with the red alert symbol with the text "Code module must be able to load."
2. I double-click any of those errors and I get taken to the offending Module pane with its red alerty symbol flashing over to the right; and in "VI Path:" there is only the VI name but not the path.
3. Click the "Browse for Path..." icon just to the right of the path, and a file dialog box opens always starting in the exact directorycontaining the exact VI TestStand supposedly "can't" find. If I use that file dialog box to select the VI manually then that error is fixed and I move on to one of my hundreds of other uninvited errors.
4. I have TestStand's search directories set correctly, I hope: In its Configure >> Search Directories... menu item I have my project's parent directory checked and its "Search Subdirectories" checkbox checked as well.
5. I tried TestStand's Tools >> Update VI Calls... menu item with the "Force Prototype Reload" option selected for the various VI calling items and that didn't work either.
How do I fix this problem?