project explorer fails with vi (folder displayed as file)

[Balze]

Norbert,

thank you for your suggestions.

I'm pretty much aware that files can get corrupt. And I understand that this is only our problem and not the probelm of NI.

Sure I'm lucky, that this VIs are still accesible and WORKING (!)

---

Norbert B wrote: 

....request that NI uses some kind of "Bit-Check" on your VI....

---

That's not what I thought of.

I'm sure that all information stored in a VI you mentioned is well organized inside the VI.

And I'm also pretty much sure that the corruption of my VIs is based on a problem that can be found inside the VI when you have the knowledge where to look at. Obviously it has to do with it's relative path.

I agree with you that a tool can't find all issues. But I guess it's possible to quickly create a tool that solves this particualr issue.

(Only if it's as simple as I described above of course.)

THANK YOU FOR THE LESSON !!

You are adding fuel to my fire !!

I discussed source code control with my colleagues some times. But theire opinion is we don't need it.

3,5 developers with some hundret projects (with same basis) but no source code control needed ?! 

Best regards,

Rainer

[Christian Mergl · Accepted solution]

Rainer,

Your VI somehow became a bad runtime menu path.

As workarround you can use the property VI>Runtime Menu Path to set the path to "not a path" or an empty path. Both solutions are working on my system.

Christian

[Balze]

Christian,

THANK YOU !

I knew the solution is out there anywhere ! 

Now I can write a little tool, that searches all VIs that come into consideration and change tis property using scripting !

This will take an hour and save lots of work !!

Thank you very much, that you did not give up and continued searching.

I'm disappointed from myself, that i didn't find this on my own 

Sad I can only give you Kudos once 

Best regards,

Rainer

Message Edited by Balze on 12-16-2009 12:28 AM