Some VIs can't be opened any more

[@nders]

Other anomalies before the failure occurend:
1. An error message appeared each time I was opening my main VI: Windows cannot find "".
LabVIEW did however load the file anyway(!) and run properly.
2. Some subVIs could not be found without assistance. This occurend after I hand checked out and in again a VI using FtpVC, se below.

Possible error trigger:
I was tying a version handling tool called FtpVC just before the error occured. It does make files read-only but does not merge or alter the files. (The file I checked out and in again can still be opened in LabVIEW).

[AllenP]

Hi,

LabVIEW will only look in certain directories for VIs. It sounds like the source code control program that you are using could be moving the VIs to another directory. You can change this information under Tools >> Preferences >> Paths. I would suggest adding the directory that your VIs are located in to the VI Search Path.

Regards,
Allen P.
Applications Engineer
National Instruments

[@nders]

Thankyou for your answer.

Actually I found out that it was an Application Builder error that caused my problem not the version control program as I had first assumed.

The solution to "Linker.ccp Error Line 2075 When Creating Executeable with Application Builder" did also work for Linker.ccp Error Line 2022 when creating dll with application builder, se http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/87b349f1f9db689e86256c910082e85b?OpenDocument.

Regards @nders