When does LabVIEW use Relative/Absolute path to find dependencies?

[James_W]

😭 They're on the same volume all that's happening for my is that I'm moving from
C:\my folder
to 
C:\my new folder
via SCC
it's on the same PC.
I don't understand why when reloading the librabries and clearing the cache it's messing up so badly.
I've tried putting the called VI in a vilib but it doesn't resolve the issue.

[JÞB]

---

@James_W wrote:

😭 They're on the same volume all that's happening for my is that I'm moving from
C:\my folder
to 
C:\my new folder
via SCC
it's on the same PC.
I don't understand why when reloading the librabries and clearing the cache it's messing up so badly.
I've tried putting the called VI in a vilib but it doesn't resolve the issue.

---

No, that wouldn't resolve the problem.  The problem is you are choosing to save your project and commit it from one location and then checking those items out to a location that completely ignores the lvproj file contents.

For a clearer picture open your lvproj file with any text editor and you will see for yourself what paths are saved in LabVIEW. 

Now, that you understand what is saved in the lvproj in SCC you have two distinct options to correct your actions. 

• Maintain the paths in the lvproj file when you checkout the source.
• Use notepad to search and replace file paths.

One of those options is not a good idea.

[James_W]

Resolved the issue thanks Jay...
It was a relative path with files checked out as externals in SVN. I've rebranched them. Fixed the relative paths in the libraries for myself and I'll work on getting trunk sorted when I know I won't break anyone else's project. (It took hacking the lvlibs and in notepad and then checking them back in to resolve.)