Labview opens all VIS in Run mode

[Jed_Davidow]

LV2013 PDS is opening all VIs in Run Mode.  This is a global problem, not specific to one or a specific number of VIs.

If I create a new VI, save it, close it and re-open it, it's in Run Mode, not Edit mode.  Nothing is set to Run When Opened, nothing is set to be locked without a password.

It's only on this installation; if I take my code to another machine, there's no issue.

I have deleted the labview.INI file, but the behavior repeats itself.

Any ideas?

[JÞB]

Check the permissions on the containing folder.  Is something set "Read Only?.  What about SCC? 

[Jed_Davidow]

SCC is not configured; I use perforce, but it's not configued to use it or to treat read-only as locked.  I have also checked out all the filed ahead of time with P4, so LV never sees them locked.  The folders themselves are not read-only.

Also, I have created VIs outside of my P4 folder, and I have the same trouble.

Example:

Launch LV:  Create a blank VI (comes up in Edit mode).

Save to Desktop (not within P4 control) as test.VI

Close

Open test.VI ---> It's in Run Mode

I have never seen this happen before.

[JÞB]

---

@Jed_Davidow wrote:

SCC is not configured; I use perforce, but it's not configued to use it or to treat read-only as locked.  I have also checked out all the filed ahead of time with P4, so LV never sees them locked.  The folders themselves are not read-only.

Also, I have created VIs outside of my P4 folder, and I have the same trouble.

Example:

Launch LV:  Create a blank VI (comes up in Edit mode).

Save to Desktop (not within P4 control) as test.VI

Close

Open test.VI ---> It's in Run Mode

I have never seen this happen before.

---

Neither have I 

I'll assume a reboot was attempted and did not change anything.  I would attempt a repair of LabVIEW from the control panel and another restart. 

[Jed_Davidow]

I just ran the SP1 update, so I don't think the repair would help.

I will try it later though.

[TBirkulosis]

What is the default program that opens VIs? Is it set to LabVIEW or something else? You can check this by right-clicking on the VI file and going to Properties. Under General you should see the default program under Opens with. You can change this by clicking the Change... button. Just a thought.

Also, can you open the VI in edit-mode from LabVIEW (versus double-clicking from your Desktop to open)?

[TBirkulosis]

Maybe you've already checked this, but this KB talks about setting the VI Properties so that a VI opens in Run Mode:

Setting VIs to Open in Run Mode in LabVIEW

Hope this helps.

[billko]

The poster mentioned deleting his LabVIEW.ini.

[Jed_Davidow]

Yeah, I checked all the options, including the Locked options.  Seriously have no idea why this is happening.

[JÞB]

---

@Jed_Davidow wrote:

Yeah, I checked all the options, including the Locked options.  Seriously have no idea why this is happening.

---

And that must be frustrating!

To help us reproduce this:

• Attach your LabVIEW.ini
• get a Jing account and attach a link to the shared shockwave file demonstrating this behavior
• attach your LabVIEW.ini file after deleting it again 
• Shut down LabVIEW
• Delete the ini
• Open LabVIEW In that order so file settings are not written upon close
• Verify it still happens

Attach LabVIEW.ini # 3

Actually I'm hoping that you forgot to close LabVIEW before deleting LabVIEW.ini and an obsolete key exists.