LV 2009 VI disengaged from project

[deskpilot]

I have noticed that in LV2009 I can open a VI without opening its project. That is, if I navigate to a vi on My Computer and open it, the associated project does not open. I'm pretty sure this is changed behavior from older versions, and was only a slight annoyance before. Now it is causing me a real problem.

I have a a VI that will be used by many others. It is in a project that hosts network shared variables. If I open the project first, then open the VI from the project and hit run, the shared variables deploy. If I open the VI without first opening the project, the shared variables do not deploy, and in fact don't exist for that VI. Meaning, if I click on them to change them, they dissapear. I put an invoke node>depoly library in the startup section of the VI, but this does not work either. The strange thing is that they do not error out on the computer that should be hosting the library, but they cannot be found from the other network computer (unless I have the project open).

[vt92]

I'm pretty sure that you have always been able to open VIs outside the project.  For your specific problem, I recommend doing a forum search for "shared variables outside project".

Here is one link that may be helpful:

http://forums.ni.com/t5/LabVIEW/DSC-VI-won-t-connect-to-shared-variable-outside-of-project/m-p/52249...

[deskpilot]

Thanks for the link, I had not found that. I think I am doing as suggested in that post, but will check my project and see what I can find. I was almost positive that you could not previously open a VI without the project popping up, not the first time I've been wrong.