Open VI Reference asking save option

[Ashwin_S]

Hello,

I am opening a VI reference to analyze the state of the VI and closing it back and repeating this process for the bunch of VI's in a folder.

While closing the VI reference, it is throwing save dialog box for the some of the VI's, after closing the dialog only  it is analyzing the next VI. To stop this behaviour I have set the  Open VI reference Option to 0x20, but still it is coming. Please Give me some way to prevent this.

[Norbert_B]

Are there any additional dialogs?

My assumption is, that those VIs are deriving from older LV versions and are not masscompiled to the current version you are using. Therefore, if you open the VI, LV developement environment will automatically recompile them, which will change the VI. So when unloading the VI, the developement environment will ask you to save unsaved changes (recompilation) of the VI......

Using the parameter 0x2 for opening the VI reference only effects the loading (supress the search dialog for subvis, do not mistake that with the "Browse for SubVI" dialog!), not closing the reference.

hope this helps,

Norbert

[Ashwin_S]

All the VI's are maintained in the same versions. Is there any way to suppress the Save Dialog alone ??

[Norbert_B]

---

@Ashwin S wrote:
[...] Is there any way to suppress the Save Dialog alone ??

---

Yes: You have to save the VI using VI Server before closing the reference......

Norbert

EDIT: If you post a small example showing your approach and the issue, we can possibly give you some alternatives....

[Ashwin_S]

Sorry I can't post the Code, but this is what I am doing

Opening a VI Reference, Checking it's Execution state (Bad,idle...) and closing the VI Reference, this should be done for all the VI's in a folder. But while closing the VI Reference it is asking to save it's dependencies, so each time I have to select "Don't Save All " option in the dialog box as all the VI's are set to read only. How can I eliminate this behaviour.

Thanks,

AshwiN

[Norbert_B]

AshwiN,

either you save the changes or you have to live with the dialogs.....

There HAS BEEN changes to the VIs (or somewhere in their hierarchy) and so you have to react on that. Could you at least post a screenshot of a dialog, showing WHICH parts of the VI/hierarchy have been changed? Are you sure that there are no changes in e.g. paths where modules are loaded from?

Norbert

[Ashwin_S]

Yes I agree you, some of the VI dependencies in the opened VI reference might have changes, so it is asking for the "Save Changes" options while closing the reference.  All the VI's are in Source control, so I can't save that VI's. I just want to read the VI's execution state and close it back, suppressing the "Save Changes".  It is an automated process for getting all  VI's execution state, so if the dialog appears then it cannot check next VI untill user select "Don't Save All" option.

AshwiN,

[Norbert_B]

AshwiN,

in such cases, a new feature of LV 2010 could come in handy for you:

You can now separate the compiled code from the cource file(s).

hope this helps,

Norbert