Office files (and the like) are very different. If you open word, excel, etc. the recently opened file list always has the path attached. As a user, you can point to the right file to load when you need it. If you were to *programmatically* open the file (e.g. through LabVIEW and active-x) you must specify the path or the program will look for the file in the current directory, which may not be the one you want. And how would LabVIEW handle this anyway? Do you want LabVIEW to search the hard drive, CD-drives and all the network drives to see if any of the vi's names are duplicated and then give you a choice as it loads? Talk about overhead! You have a 3 choices: rename the files, load the vi's dynamically with the right path, or as the other responder said, use the vi hierarchy window to make sure the proper vi is being used. I find it good programming practice to append a version number to all vi's that changes each time I make a major change to a vi. Sometimes this isn't practical, in which case you need to use the vi hierarchy.
Dave.
