Every time I open my project file (LabView 8.5) it needs to be re-saved

[Ben]

To option come to mind.

1) Find the offending VI and do a "save as" to a unique name and a folder with the rest of your code. You could just prefix the name with AAA for example.

2) Trick LV by opening the VI you want to use explicitely and THEN opening your app. LV will use the VI already in memory and will forget abou the other one.

Ben

[Edjsch]

Actually, before your reply, I ignored the warning and forced the replacement with the 8.5 version, and, of course, saved every time. They all were accepted and the application still works :-). But the damn (excuse my French) project file still opens with the asterisk! I double-checked every dependency's properties and confirmed that it is the 8.5 version. What gives?

[Ben]

"... (excuse my French) ..."

No problem here. I'm and ex-sailor and know how to conjugate the word f%#$.

Did you try to mass compile?

ctrl+shift+run_arrow

Ben

[Matthew_Kelton]

---

@Ben wrote:

"... (excuse my French) ..."

No problem here. I'm and ex-sailor and know how to conjugate the word f%#$.

Did you try to mass compile?

ctrl+shift+run_arrow

Ben

---

Or right-click on the project (top-level tree item in the project explorer) and choose Mass Compile.  This will recompile every item in the project.

[Edjsch]

Ok. I did  the mass compile, and still the same problem! This is the dialog for the mass compile:

#### Starting Mass Compile: Tue, May 13, 2008 12:14:00 PM
  Directory: "C:\Documents and Settings\<my name>\My Documents\LabVIEW 8.5\<my folder>\<my project name>.lvproj"
  ### Bad VI:    "<my project name>.vi" Path="C:\Documents and Settings\<my name>\My Documents\<my folder>\<my project name>.vi"
#### Finished Mass Compile: Tue, May 13, 2008 12:14:03 PM

I don't know what's bad about it. It still works?? Any ideas?

[Ray.R]

Do you mean that if you open the BAD VI that is located <e-x-a-c-t-l-y> in the folder described in the Mass Compile, that you can run it?  As in running that one VI by itself?  And after running it, if you go under properties and look at the path, it also matches the one in your mass compile?

I've seen something like this recently.  Someone had copied the poject I was working on and pasted it to another location.  Little did I know that when I was opening the project, it was pulling the file from this guy's new location (he must have done something somewhere... we won't get into that).  However, I was not catching it with a Mass Compile.  I found the new clone (copy-cat) of the project and removed it.  Started the project and it claimed the one nasty VI was missing.  Linked it to the original one from the project and everything was fine afterwards. 

So maybe you are in the same predicament.  The Bad VI may not be loading and when running the project, a copy of this one may get loaded. 

Strange things do happen in life.

RayR

[Edjsch]

No. I found the problem with the bad vi. The one I opened and ran was my working version, but the project file (naturally) points to the final name of the vi, which was broken somehow. (One sub vi from the ExcelExamples.llb was missing for some unknown reason.) I replaced the missing vi with the correct one from the 8.5 llb, and now I don't get the "bad vi" error message. Whew!

(The missing one was: ExcelExamples.llb\Open New  WorkBook.vi. Notice the 2 spaces between New and WorkBook? But it's that way in version 8.2 also.)

I went through all the dependencies again, and they all point to the 8.5 version, but I still get the (&$%&@#) asterisk.

As I said, the 8.5 project was "migrated" from version 8.2 originally by cloning the appropriate files to my new 8.5 folder (in My Documents) and saving all. But several of the sub vi's (all in llb's) were still being pulled from the LabView 8.2 examples folder. Now that I've corrected all of them, I expected this to solve the asterisk problem, but no dice.

How do I locate the offending vi(s) (if this is the problem)? (I didn't go through each and every vi in the dependencies "vi.lib" tree (there's over 100 of them), but all I looked at were correctly from the 8.5 tree, as they should be.)

When you open the project file, do you get the *?

Message Edited by Edjsch on 05-13-2008 01:53 PM

[Matthew_Kelton]

OK, so I have a project that is doing the same thing as yours and I found a way to get it to not happen.

Do you have any autopopulating folders?  My project does and everytime I open it, it indicates it needs to be changed.  Once I turned off the autopopulating folders, it no longer did that.  Turned them back on and it was back.

[Edjsch]

Not that I'm aware of. Where do I find "autopopulating folders"?

[Edjsch]

Ok, I found it, and changed my 5 folders for my app to "stop autopopulating" and no more *. Do you know why?