DSC VI won't connect to shared variable outside of project

[SamboNI]

Hi Brian,

I have figured out what is going on here. When you drag the shared variables from the project explorer window to the front panel, then the "data binding" tab of the front panel controls will be referenced to My Computer (project referenced).

So, since the project does not exist when you open the VI independently, the shared variables do not know where to look. You will want to right click on them, go to the data binding tab, select browse, and choose network path. Once you have your library deployed, you will be able to pick the variable to which the front panel control is bound (and these shared variables will only work after you have used deploy library.vi

I have uploaded the VI which shows this, you will just need to change the computer name in the data binding to your computers name instead of mine.

Hope that clears things up! Let me know.

Best regards,

[SamboNI]

Hi Brian,

To answer your earlier questions:

>The data binding properties of the variable in the standalone VI are lost for some reason.  The path to the library is blank.

This appears to be some sort of a bug, where project referenced variables do not show the path when the VI is opened independently of the project. I will file a corrective action request regarding this.

>Another thing I don't quite understand.  If I have a library called "My Library.lvib" in folder "c:\My Libraries", the data binding path for the variable in the working VI gets changed to "My >Computer\My Library.lvib"  Why is that?

The reason for this one is that you have dragged them from the project explorer window, and therefore the data binding is referenced to the library within your project, and not the network.

Best regards,

[SamboNI]

To follow up for those who are interested, the CAR ID for the issue of opening a VI with front panel controls bound to shared variables and empty paths has been filed with ID 43EAFDRJ.

The other issue, of a VI with the property of run when opened not executing when double clicked from project explorer (and just going into edit mode) was filed under CAR ID 3NOD8AMX . However, this was closed as not a bug, as it is expected behavior to go into edit mode for a VI when launched from the project, even when the "run when opened" property is enabled.