LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

continually prompted to save changes to vi

 

hello.

 

each time i run a vi, i am prompted to save changes to it.

simple search shows the following solution.

http://digital.ni.com/public.nsf/allkb/19C57EBCDDA4B31586256B53007C538B

yet, this does not work when compliling either the library of te file in question (error.llb) or its parent directory.

 

Here is a screen shot of the messasge.

 

 

This is NI labview 8.6

the code happens to be running on a crio 9014 if that matters.

OS vista 64

 

Any ideas?

0 Kudos
Message 1 of 7
(3,204 Views)

Are you using probes?

 

I've seen this message pop up when I place probes on the BD of a VI running on a cFP target.  I'm not sure why, and it is kind of annoying.

0 Kudos
Message 2 of 7
(3,181 Views)

 

 

we were using them and there still may be a few probes down.

 

Ill check it and report back.

Message Edited by jimmyinCT on 09-26-2009 04:58 PM
0 Kudos
Message 3 of 7
(3,178 Views)

no, there were no probes in the target.

 

 

its really annonying to have to see this everytime we run the program

0 Kudos
Message 4 of 7
(3,124 Views)
Are you using any X-Controls? X-Controls have the attribute of whether to save their state or not. If the X-Control is saving its state this can lead to the behavior you are observing.
Message Edited by Mark Yedinak on 09-28-2009 06:55 PM


Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 5 of 7
(3,119 Views)

 

there are no x controls orin the file

 

Message Edited by jimmyinCT on 09-28-2009 07:04 PM
0 Kudos
Message 6 of 7
(3,112 Views)

 

Its not related to the crio

 

I found another file which gives similar behavor

The example for "write to spreadsheet.vi", which is titled "email with data"

Also continually prompts me to save this file of which, does not seem to be in use.

This is the only other file which has the same behavior so far

I get hte message regardless of where the vI is run

Message Edited by jimmyinCT on 09-28-2009 07:11 PM
Message Edited by jimmyinCT on 09-28-2009 07:12 PM
0 Kudos
Message 7 of 7
(3,107 Views)