LabVIEW prompts to save the vi when closing the reference

[SAS]

In our application, we - Open vi reference - finding its execution state - closing the vi reference. While closing, LV prompts to save the vi, how to avoid it. I can see option to enable LV prompt, but no option to skip it. We use 0x20 for now to avoid the loading dialog.

We appreciate your input

Thanks

Sas 

[SAS · Accepted solution]

Looks like when leaving the option to 0x0 or using anyother option other than 0x4, it should not prompt the user to save the file. But for some reason, i have faced the user prompts to save the file ...Dont know why!!! but got the solution now 🙂

It will be good to know why i got the prompts even for option 0x20!!!

Thanks

Sas 

[billko]

The only reason why I would think a VI would have that prompt is if something changed.  Sometimes a sub-VI gets loaded from a different path than when the VI was built.  Did you ever click on "Explain changes" when the save option comes up?  That usually explains why the VI thinks it needs to be saved.

Bill

[TheQ]

FYI

The VI will be considered "changed" if it had been saved in a previous version of LabVIEW and is being opened in a newer version, even if nothing else has changed.

[InfiniteNothing]

What was your solution? I'm seeing the same issue. I'm opening the VI and closing it with VI server and it's asking me to save. It is correct in that the VI was modifed and does need to be saved but I did not use the 0x04 option and it should not ask me to save.

[Hooovahh]

I have seen this in the past with scripting VIs and I tried to resolve it but couldn't.  So my solution was just to supress the dialog temporarily.  Darren posted over on LAVA a VI that does this.

http://lavag.org/topic/17845-silently-close-a-scripted-vi-with-unsaved-changes/#entry107546

I believe this just calls the private method App.UnattendedMode

[InfiniteNothing]

Thanks. Do you know if there is a CAR for this issue? I'm not even using any scripting, just the normal VI server.

[Hooovahh]

I do not know of a CAR for this. I couldn't ever get it to be easily reproducible so I never talked to NI about it.

[Hooovahh]

Oh by the way for me I found it on LabVIEW 2011 SP1