problem with executable: looking for an unkown saved instance

[will_fr]

hello !
i'm working on labview 7.0
I have made a program and i always make and use the executable without any trouble. i have made some change (i have remove a page in a tab), and know the executable is always asking for "instance 3117 saved nameofthetoplevelvi.vi"... and obviously doesn't want to work anymore!? The point is that when i use the top level vi (not the EXE) it works well! is anybody knows what's wrong and how to solve that issue?
Thanks in advance

[mfitzsimons]

Only thing I can think of is to check ALL Properity nodes associated with the TAB Control.  Sometimes by deleting a tab can mess up the properity nodes that act on the control.

If not using properity nodes then I have no clue.

Matt

[will_fr]

thank mfitzsimo…
i have replace the tab control by a new one, so i have replaced all the property nodes, but it is still the same...
another good idea?

[mfitzsimons]

This looks like a deep LV issue and could be ugly to resolve.  If you have access to tech support start there.  If not, if the differences are small start with a known good chunk of code and make the same changes.  I am assuming that from your email that you have been using and building this app just fine for a period of time then it crashed?  Anything that you have changed can be suspect.

Matt

[will_fr]

i don't think that it come from LV directly (well who knows...) but when i use the previous version of the program i haven't got that pb...
well i think i have to start back with that previous version and re-make the changes, but it is time consumming!
so if anyone has THE solution...

[mfitzsimons]

I guess at this point it wouldn't hurt to try to Mass Complile the problem VI.  See if it throws an error.

Good Luck,

Matt

[will_fr]

well i haven't done that before, can i ask you the way to do that?
thanks

[mfitzsimons]

Tools => Advanced => Mass Compile

Try it first on the individual file.  I you change versions of LabVIEW it will bring your VI's up to the latest version.  Like if you go 7.0 to 7.1 you want to Mass Compile all of your VI's to bring them up to the latest version otherwise it will have to do this every time you load an older file.  It is a good idea to ZIP of Source Control your files before running Mass Compile.

Matt

[will_fr]

i have done th emass compile, obviously it hasn't solve the pb, too easy !
well il log file, a lot of #BAD VI appeared : what does that mean? should i do something with them?
thanks for the time you take for replying

[mfitzsimons]

It usually means that the VI's are not executable.  If they are old you many of broke them in a differnt version.  If they are important then this is a bad thing.  They need to be fixed.

Matt