From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
01-16-2017 08:19 AM
Hi,
We have a subcontractor who has developed a VI for us that includes several sub-VIs that they won't give access to. Consequently the sub-VIs have been provided without the block diagrams. Now I struggle to build the VI into an application and I get the error : VI cannot be converted to the current version because it has no block diagram.
Question is: Is it me doing it wrong or is it true that VIs without block diagrams can only be used in same version same operating system etc?
If so how should the subcontractor share the sub-VIs with me so that I can use them?
What I really want to do is make some minor changes to the main VI and re-compile it to an application.
Thanks
Solved! Go to Solution.
01-16-2017 08:27 AM - edited 01-16-2017 08:28 AM
Hi CAP,
Question is: Is it me doing it wrong or is it true that VIs without block diagrams can only be used in same version same operating system etc?
Yes, that's true: you need the very same LabVIEW version! (OS is not as relevant.)
When the block diagram is missing the VI only contains the FP and the compiled code: you need the same LabVIEW version to be able to run the code.
If so how should the subcontractor share the sub-VIs with me so that I can use them?
They need to provide either the blockdiagram - or you have to agree on the same LabVIEW version!
What I really want to do is make some minor changes to the main VI and re-compile it to an application.
Then you need "runnable" subVIs as described above.
Lesson learned: when buying code from a subcontractor you need to have a contract which allows access to the source code (aka block diagram) too!
01-16-2017 09:11 AM - edited 01-16-2017 09:14 AM
If so how should the subcontractor share the sub-VIs with me so that I can use them?
To expand on this a little more than GerdW did... a better method (in fact the method that NI uses) is to just have your subcontractor password protect their VIs.
This article gives you a little bit better reading on password vs remove block diagram. Removing block diagram is technichally more secure, but password protecting is still secure and allows for recompile to other versions of LabVIEW.
Edit: clarity
01-16-2017 09:16 AM
Some additional reading: What Happens When I Save My VI and Remove Diagrams?