For the record, this is how CVI 6.0 fixes up paths of moved files:
If the project is moved to a different letter drive, and if files contained in the project are not under the project's folder (or subfolders), then CVI 6.0 will not be able to "fix up" the file paths. For example if I have project1.prj under the following directory structure:
c:\temp\myproject\project1.prj
c:\temp\myproject\main.c
c:\temp\myproject\main.h
c:\temp\myproject\main.uir
then when I move project1.prj (and its files) to:
d:\temp\myproject\project1.prj
d:\temp\myproject\main.c
d:\temp\myproject\main.h
d:\temp\myproject\main.uir
CVI will be able to resolve the new paths because the files are at the project level. However if the files were located in an unrelated directory, a
s such:
c:\temp\myproject\project1.prj
c:\anotherfolder\main.c
c:\anotherfolder\main.h
c:\anotherfolder\main.uir
then when you move project1.prj (and its files) to another directory, CVI might not be able to fix the paths of the files under "anotherfolder". This is directly related to how CVI stores filepaths. There are two choices, relative vs. absolute path. Relative paths are easy to fix since they are relative to the project file. Absoluate paths are not "fixable" and cannot be changed.
By the way, the next version of CVI will be able to find files anywhere, even across driver letters, regardless of their location relative to the project file! If you are interested in checking out the next CVI (beta), go to ni.com/beta
Regards,
Azucena
