VI Properties:Protection:Locked does not persist

[DEppAtNGC]

I set a top level vi to VI Properties:Protection:Locked and it behaves as I expect (the window appears similar to Operate:Change to run mode). I save the VI and then close it. When I reopen the VI, it is in edit mode, not locked as I desire. I can set Options:Environment:Open VIs in run mode, but that changes the environment for all vi's; I only want this one VI to be protected. Is this a defect, or am I missing something? Thanks!

[mikeporter]

From what you are describing it sounds like you are doing things correctly. Are you providing it with a password? Also when you reopen it, what happens if you press Ctrl-E?

Mike...

[DEppAtNGC]

I'm using locked - no password. I am saving into an .llb and this VI is marked top-level (but it behaved the same when I saved to a .vi as well). When I double click from the LLB Manager, it opens in edit mode. Ctrl-E opens up the block diagram editor.

[DEppAtNGC]

Let me state that my primary objective is to save the vi so that it comes up in Operate:Change to run mode so that the user does not see all the grid-lines and mistakenly edit the vi. I do not want to set the Tools:Options:Environment setting because that applies to all vis - I just want this one to come up in that mode. Also, in general, it seems that the locking is broken - I tried lock using a password, and I get the same behavior - I can see the block diagram.

[mikeporter]

Son of a gun, you're right it doesn't work...

Mike...

[Spex · Accepted solution]

This behavior was reported to R&D (CAR# 128657) and fixed in LabVIEW 8.6.1.  The work around for locking a VI in LabVIEW 8.6 is to save the VI with password. 

Saving the password may have appeared to not function for you because LabVIEW caches passwords after you apply or enter them on a development machine.   LabVIEW will remember passwords in the cache until you clear the password cache either by exiting LabVIEW or manually clearing the cache in the LabVIEW opt...

Cheers,

[DEppAtNGC]

Is there a patch? I really hate to have to install 8.6.1 all over again - primarily because of internal issues about who keeps the disks and who performs the installs. Thanks! David

[ColeTrain]

DEppAtNGC,

National Instruments generally does not issue patches for something that has been solved in another version.  But, with that being said, is there any reason you do not like the work around that Spex put forth?

[DEppAtNGC]

I don't really want to lock the VI, as mentioned above, I simply want this VI to appear in Run Mode, not Edit Mode. Please read above carefully.

[ColeTrain]

DEppAtNGC,

I understand you don't want to lock it, but unfortunatly that's out only solution short of installing 8.6.1.