03-18-2020 04:20 PM
The following errors have come up in a program I am working on. They both seem that the respective library can't find the VI but I've checked the program files and the files are included in the library so I'm not sure what the error is.
03-18-2020 04:34 PM
Hi,
The first error looks like is caused by a call of a VI outside of the library trying to call a private member of a library. I don't know how are you managing the elements in that library, but from the project explorer you can choose to the access scope by right clicking on each element. The following link explains better ow to change this: Setting the Access Scope of Member VIs
For the second error it seems that the library is not recognizing an element as its own, but the VI is saying that he is part of that library. Here it is important to know that LabVIEW libraries store a list of all its members, their location, and not only that, each member of that library, also knows if it is part of a LabVIEW library. So it sounds to me that you restored the labview library to a point where the library didn't have that element. Or also it could be that you deleted the element from the library, saved the library, but didn't save the changes on the VI. So the VI still thinks it is part of that library.
I hope I was clear enough.
04-06-2020 11:02 PM
Unfortunately, because I have to use LabVIEW2015 for project reasons that feature doesn't seem to be available. When I go through the program (x86) files and go to the classes these VI's are owned by they seem to own all the items they are trying to call.
04-07-2020 09:27 AM
As mentioned, both the VI and the library keeps information of if it's part of a library and if so, which. If they don't sync up this can happen. I think you can save it by r-clicking it in your project and "remove from library". Else you can create a new VI in the library and copy-paste the content to that one.