i got it! thanks guys
i had a windows crash which lost me all, or a lot of the paths to my vi's...
but i have it sorted now, thanks!
"Al S" wrote in message
news:50650000000500000071AB0000-1031838699000@exchange.ni.com...
> I suggested a mass compile because of the error message you received:
> "the call back vi is too old for my ver of lab view". If the Test
> Executive can't find some VI's, that may be another problem.
>
> Did your hard disk crash or did Windows just crash?
> Did you reinstall your VI's or just the Test Executive?
> Are you sure you reinstalled your VI's into their previous
> directories?
> Did you need to reinstall LabView?
> Are the VI search paths different now? See the search path in LabView
> 6
.1 at Tools >> Options >> Paths >> VI Search Path.
>
> If LabView can't find a sub VI, it will show you the complete original
> path to the VI (including the LLB file, if any) while it's searching.
> After completing an unsuccessful search, a file dialog will open
> asking you to find the missing VI. In that dialog, it shows only the
> vi name, not the complete path. But you can move that dialog out of
> the way to see the complete path in the search dialog behind it.
>
> If you realize that the VI or LLB was moved and you want to restore
> the original location, you can stop the VI load, exit LabView, move
> the VI or LLB using Windows Explorer, restart LabView and load your
> application. If you want to use the new location, browse to the new
> location to locate the VI when LabView prompts you to find the VI.
> After the load is complete, exit LabView. It will prompt you to save
> calling VI's recompiled because sub-VI's were moved. After that save,
> LabView will find the VI's
next time you load your program.
