Labview Save File Nightmare!

[Jon Hart]

Hello,

I am working on a large project which calls upon many sub VI's which often are 3rd party supplied.  Whenever I make a small change to a VI and try and run my project (it's a real-time cRIO based app), Labview prompts me that a completely non-related VI needs saving.  Often it is a VI in a 3rd party LLB that CAN'T be saved because I dont have necessary access rights.  If I say cancel, I can't run my project because Labview says "You can download and run without saving".  This is driving me nuts!

I stress, the unchanged VI's that "need saving" (not) have not EVER been changed by me as they are 3rd Party or NI supplied.

Any ideas?

Regards

Jon

p.s.  Please don't ask me to post the code as it is enormous and dependent on lots of 3rd party VIs.

[AdnanZ]

Hi Jon,

Hope you are doing well today! I don't see a reason as to why you should be getting that dialog if it is third party supplied and you don't have access to the VI. I would suggest mass compiling the directory even though I am not sure if that would help. Is it possible for you to only post one of the NI VIs or a third party VI that is giving you this issue?

[Graziano]

Hi!
  When you're prompted to save that VI, select "Explain changes..." button.

   I suppose that third party library rely on some other LabView libraries, that were located in a different location on the PC where third party libraries have been developed.... but actually I don't know, I'm only guessing

    Anyway, please, report what's written in "explain changes..." window, so that we can help you a little more.

   Have a nice day!

graziano

[lmtis]

Often some of the third party packages have been developed in an older version of LV, and LV will want to save them for the version that you are running.

[Ray.R]

Does the 3rd party code have documentation describing what it does and any limitations that the code has? 

When buying 3rd party code, make sure it has documentation. 

[Ben]

I'll jump to the game of trying to help with very little to go on.

Try setting all of the third party VI's as read only and then check both of the boxes shown below to see if that gets rid of those messages.

Ben

PS: Thanks to Mike Porter for teaching me this last night.

Message Edited by Ben on 04-29-2008 08:46 AM

[Jon Hart]

It's not that simple as it isn't always the same VI, but usually it is to do with ones that use "General Error Handler CORE.vi".  So for example, just now I loaded the project from scratch, opened my GUI VI, then closed it (making no changes) 

It tells me that NI_3dgraph.lvlib:Basic Properties.vi has unsaved changes

Affected Items:

NI_3dgraph.lvlib:Basic Properties.vi

NI_3dgraph.lvlib:3D Surface.vi

Format Message String.vi

General Error Handler CORE.vi

If I click "Explain changes", all the above items say "VI recompiled".  The top two also say "External component modified since last VI Save"

Any Ideas?

[Jon Hart]

Thanks Ben,

Looked promising but no cigar 😞

As you can see NI_3dgraph isn't a third party control.

[Ben]

Try doing a mass compile.

Warning: that can take a while.

Ben

[Jon Hart]

Ben,

That has done the trick!  Will let you know whether it is a complete fix further down the line.

Cheers for now!