Picking up where someone else left off...

[K2Web]

Good Moring all,

Like everyone who has ever taken on a new position and has had to pick up where their predicessor had left off, there are typically tons of questions (particularly when the predicessor had left the company.) My particular question is regarding an error converter sub vi that I can not open and is vague in its reference to its parent vi. I am have used LabView in the past but I am quite rusty. I can not tell if this is a standard sub-vi fromthe 2017 version Labview set up or if it is one my predicessor had made and is now broken? I am attaching the sub-VI and its parent for refference. Any direction on this issue would be greatly appreciated.

Kind regards,

Karl

[paul.r]

Looks to be something custom - I cannot even open the subVI, I am getting an error message about missing dependencies that wont allow me to open.

[K2Web]

That was my thought as well. However I am tasked with making this program work and this is small (but important) portion of the code (as you noted) will not open. This was not the case last week though and I am wondering what could have happened that would cause this VI to stop functioning or even open for that matter.

[paul.r]

Are you connected to a network drive? Opening the VI in a text editor seems to indicate that it is looking for some files on a networked drive. If that is the case and you arent currently connected to the network, that could explain why it was working and then stopped. 

[K2Web]

Would moving all the related files to a new location and rebuilding the application (or attempting to anyway) solve this? I had tried this where I had found all the information and again when I created a more logical placement on our server

Best Regards,

Karl

[paul.r]

It should, however you need to start with the files in their original location, and then use the project explorer to move them, with the VI in question loaded in the project explorer when you move them. 

[K2Web]

So here wasm the odd solution to this issue. There was a naming convention change that was not allowing for the files to identify the source path correctly. I had to go through each file and one by one check all of the names as they were originally called out in the source file. Time excessive, but effective.

[Mark_Yedinak]

I hope you are doing this with a LabVIEW project. If not, you should. Project files help to manage all of the path stuff and makes moving files much easier. The y also help to reduce cross link errors.