Cannot get a VI to save

[EdDickens]

I'm working a project I did a couple years ago in 8.0.1. Nothing fancy, but it's a fairly large application (almost 1000 subVIs including vi.lib stuff) controlling a test stand using an M series and DIO PCI boards.

In the Project, I have three libraries (.lvlib) containing all the files. Suddenly yesterday, I could get the top level VI to save. I can select Save (or Save All, Ctrl+S...) and the VI will save. The asterisk in the title bar goes away during teh save process, but comes back on after the save is done. Closing the VI prompts me to save changes. Listing the changes give me:

• VI Recompiled. - Changes to front panel data structure or block diagram data flow causes LabVIEW to recompile the VI, generating new execution code.
• SubVI Call(s) Modified. - A subVI's connector pane (or a polymorphic subVI's list of VIs) was modified. Show the Context Help window for the subVI and make sure the connections to the subVI on the block diagram are still correct.

The top level is the only one showing any changes. I can save from the Close dialog and the asterisk will be back when I reopen it.

I've tried a complete compile using the "Shift+Ctrl+Run" and a mass compile on the project directory. Rebuilt the libraries and the project. Copied the code to a new VI diagram. Nothing does the trick.

It does this on both my laptop and the test stands computer, so it has to be something in the code.

Anybody ever have this happen?

Ed

[CMal]

Ed,

Have you checked to see if your files are in a "Read Only" folder.  It's a long shot, but the only time I've seen anything like what you describe has been when I forgot that I was working with "Read Only" files.

-Chris M

[EdDickens]

No, it's not a Read Only problem. (I did check just to be sure)

It just started happening in the middle of developing. I think you get a dialog stating that the VI can't be saved when the Read Only attribute is set, but I get nothing. It acts like it saves. The save date/time stamp on the VI updates, but the asterisk is always there and it always prompts to save when I close it even if I've just manually saved.

Ed

[dan_u]

Hi Ed,

I've seen this too. In a rather large projects we had some VIs (and I think we still have, I stopped bothering) that would just after saving appear as modified again.
We haven't found out what's special with these VIs so we don't know what causes this problem.

Sorry I can't give you any hints, just wanted to tell you you're not alone

Daniel

[Eriquito]

Hi Ed,

I looked through our archives to see if this problem has ever been encountered before.  It has, but is fairly uncommon and a solution was never found.  If you can try to find which VI(s) are causing the problem, and post it here, I will see if I can reproduce the problem and launch an investigation into its cause.

[EdDickens]

Thanks Eric.

I actually managed to fix the problem today, but I do have a backup from Friday. I'd rather not post the code here. Can we take this offline?

Half of my application is disabled using the Diagram Disable structure and the problem was in the code in the disable structure. I didn't take the time to narrow it down to a specific VI(s), I just needed to get it fixed.

Let me know if you still want to look into the problem and I'll send a copy of the code.

Ed

[Eriquito]

Hi Ed,

If we are able to reproduce the problem on our end, we can determine if it is a bug or not and (if so) file a Corrective Action Request (CAR) with our R&D department so that it can be fixed in future releases.

Please visit www.ni.com/ask and create a new email support request or phone support request to send us the VIs, if you are willing.

Thanks!