Please see errors listed on the library.

[jvh75021]

I have subVI error:"The VI's owning library has some problem. The library has blocked the VIs that it owns from executing until the probelm is resolved. PLease see errors listed on the library.

I am looking at the library and see no errors. What incantation would be appropriate to get it to show me some?

thanx,

jvh 

[tbob]

Which library are you talking about?  You need to attach your code.  We have no idea what you are talking about.

[Ben]

---

jvh75021 wrote:

I have subVI error:"The VI's owning library has some problem. The library has blocked the VIs that it owns from executing until the probelm is resolved. PLease see errors listed on the library.

I am looking at the library and see no errors. What incantation would be appropriate to get it to show me some?

thanx,

jvh 

---

In early versions of LVOOP it depended on the phase of the moon.

In LV 2009 look at all of the errors for all of the VIs and I THINK work form the top down.

The message is telling you that something in one of those libraries is broken. There is a bug in the current version of LVOOP where one of the child classes can break the parent and the other siblings go the same way.

If you look at all of them and can't see an issue check the protection on dynamic VIs to make sure they all have the same setting and if you changed an icon connector, make sure all of the dynamics are using the same pattern.

I probably should have stopped answering after the first line.

Ben

[Verne_D]

Hi jvh,

I'd be interested in looking at this code too. What version of LabVIEW have you been building this in?

[Jacc]

I encountered the same problem in LV 8.6.1. I suspect that I created the problem when I copied a class from another project into this project and then modified it. However, before I modified it, I had it inherit a parent class in the project, so the class was broken when I set up the inheritance.

The solution was to play Scrooge and disinherit all classes from all classes. Then, the copied class was the only class that still exhibited the error. I then removed both the parent class and the copied class from the project, added the parent class back into the project and exited LabView. I created a new copy of the copied class, opened just the copied class in LV and made changes to VIs and controls until there were no more errors except for not inheriting the parent class. I then inherited the parent class and closed the class. Finally, I opened the project and added the class to the project. I'm not sure all steps were needed but all was well thereafter.

In the future, I plan to set all class properites (icon, wires, etc.) when adding a copied class, but leave inheritance alone until I have made all modifications.