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.

LabVIEW

Author

Frank,

We did eventually solve this problem by doing the following:

Don't use any Auto-populating folders.

Don't use the General Error handling on the RT system - replace with logging to a file.

Cheers

Jon

Message 31 of 31

(524 Views)