an attribute of the project was changed

[jefska]

I've upgraded labview from 8.2.1 to 8.5 and I have done the same with a project.  Now, when I try and close the project it comes up the the Save Changes dialog even though I have not made any changes since saving under 8.5.  I have tried a mass compile and that didn't solve the problem, it still thinks there is an attribute that has changed.

Please help.

[MikeS81]

Hi jefska,

do you have some Auto-populating folders in your project? This could be a reason for it.

Mike

[jefska]

Thanks Mike for the reply.

I don't think I have Auto-populating folders in my project.  I have folders created in libraries but this wasn't an issue when the project was ver 8.2.1.  Also I have other projects that are 8.2.1 and when I save them in 8.5 I have the same problem.  Any other suggestions?

Regards.

[Vsh]

ok,

If you have vis created by you, but not under the folders in the project and they are under dependencies, move them to your folders under the project.

This should solve the problem


Message Edited by Vsh on 04-08-2008 02:23 PM

[jefska]

The dependencies in my project are part of the labview 8.5 software and not vis I created, folders "vi.lib" & "instr.lib" and a dll file.  In my 8.2 project there were no dependencies but when I upgraded to 8.5 now there are.  Any thoughts?

[David_B]

When you say you tried a mass compile, did you mass compile the LabVIEW 8.5 folder as well?  If not, give that a shot.

[parthabe]

Hi David,

Why the LV 8.5 folder needs to be mass-compiled? Anyhow all its components are already in LV 8.5, right... ?!

I cant understand. Can you explain more?

[Vsh]

When I had the same problem, I tried with mass compilation. But did not help. And then once I moved the vis in dependencies to folders (but not to correct this problem though)

But very soon, this problem was solved!!!. Perhaps I thought may this was the problem

[jefska]

I did a mass compile on the LV 8.5 folder and it didn’t help.  Is this a possible bug in 8.5?

[David_B]

To answer the earlier question of why the LabVIEW folder:  What Does Mass Compile Do in LabVIEW?   Basically, it relinks all subVIs to main VIs, checks for corruptions, as well as updates to the latest version.

Are you by chance using Teststand at all?  If so, this may be related: Why Do My VIs Open with Asterisks After Being Mass Compiled in LabVIEW for TestStand?

Really, I imagine that one of the VIs in your project is still somehow not updating it's links to the new subVIs.  Can you post one of the projects that is exhibiting this behavior?

One thing you may try is to save a copy of the entire project (one of the save as options) and see if the copy acts the same way.