SubVI missing, but visible in windows

[Casey]

Hi Chris-

Wow.  Okay, it's good to know the answer.  Unsurprisingly, I have more questions:

1)  Will pasting the entire block diagram into a new VI cause the new, formerly blank, VI to become corrupt?  It seems that sometimes I can open the block diagram of the corrupt VI, and other times I can not.  I haven't tried to paste the entire block diagram yet, because I'm too busy trying to meet my deadlines.

2)  What could cause this?  I'm very concerned because it's happened to me twice already.  Both times to the same file, and both times when VI server exited the VI in a way that was "funky" or unintended.  Do you have any tips for keeping VIs uncorrupted?

Thanks,
Casey

[AESulzer]

Casey,

To address your questions...

1. It depends on the corruption. If the corruption is tied to an object in the VI (often call an "insane object"), then the corruption will most likely carry over with the object when it is copied. However, if the corruption is in the general VI portion of the code, then the corruption may not carry over during a copy. The only way to really find out is to try it!
2. That's the million dollar question! In theory, a VI should never get corrupted, so if we know of a way that LabVIEW corrupts VIs, then we are already busy fixing it. If you can find out a way to consistently corrupt a VI inside of LabVIEW, then plase let us know about it, and I will pass the information along to R&D. The best thing you can do as a LabVIEW programmer is to always keep frequently updated backup copies of your VIs to insure against any unforeseen calamities that may arise in the future.