"corrupt VI" error popup when opening subVIs

[RogerK]

I am using LavVIEW 2009 SP1, Widows 7, 32 bit.

As I develop a program, I frequently open and close subVIs.  About 1 in 10 times when I try to open a subVI, I get a popup window that says:

"The VI myVI.vi has changed on disk since last saved or loaded by LabVIEW.  If you load its front panel, it will probably be inconsistent with the parts of the VI already in memory, resulting in a corrupt VI."  There are "Revert" and "Cancel" buttons on the popup.

When this happens, I chose cancel, then completely close and re-open LabVIEW.  Then it lets me open the subVI with no problem.  I always open subVIs by double clicking them on their parent VI block diagram.  When I close them, I always save chages.  If my changes result in the subVI being grayed out on the parent block diagram, I immediatly right click and relink to subVI.

Is there something can do to prevent this?  Thank you.

[PatJamSim]

Hello Roger,

After doing some digging, I was able to find a few older Corrective Action Reports that resolved this message in some scenarios, but it looks like the message itself isn't necessarily a bug.  I also found this forum thread that goes into some good detail on what's happening:

http://forums.ni.com/t5/LabVIEW/Labview-8-5-prompts-me-when-I-change-a-subvi/td-p/579867

Basically, the VI you edited has some minor difference from its own source.  This can result from a few causes, most of which are discussed on that forum.  When you select Revert, it should write the changes you've made into the file, which doesn't exactly line up with what you would assume "revert" entails, but is supported in that thread by what LabVIEW users were experiencing.

I believe that launching the subVI from the project explorer will allow you to open the subVI without getting this warning.  Is this the case for you as well?

[RogerK]

Hi Patrick,

Thanks for the reply.  As the OP said in the post you linked, At least now I know there is nothing really wrong.

Out of curiosity, how did you find that post?  I only posted after searching the forums and not finding any applicable information. 

[ShishKeBobby]

Hey RogerK,

We get really good at searching for LabVIEW stuff after a while