Disappearing properties/methods with activex reference requiring a relink

[GregFreeman]

I have a strange feeling this is related to activeX inside a class. I have a class with an activex instrument driver whose reference is contained inside the class private data. I am running into some situations where after closing and reopening LabVIEW (sometimes committing to SCC and opening on another machine) my app will crash. When I find the offending property node/invoke node that's crashing, I will click it and get a greyed out "no properties/methods" shown. But, if I go to the source node that provides the input reference to the downstream node, and change the property, then change it back, it updates the downstream node and all the properties/methods reappear. Has anyone run into this? In the example below (not my actual code but just used to show what would happen) If I clicked the save node it would show no methods, but as soon as I changed Project.New to something else, then changed it back, the project.save node would relink properly.

In case it matters, this is some older code written in LabVIEW 2013.

[CanadaGuy]

Yes, I believe I have seen what you described, but it is not predictably reproducible, at least in my situation. I don't really have any solution to it, other than re-linking it as you described.

[GregFreeman]

Did some more digging. By chance an invoke node was copied and pasted to another block diagram and we got these errors. Looks like the property nodes themselves are still coupled to an old version of the library that we upgraded at some point. Even after we relink and the methods/properties "reappear" the copy and paste still shows this error. The only way we can find to get rid of this problem, even after rewiring up a reference to the node itself, is to physically delete and recreate the node. 

[Ben]

That sound a lot like the situation we see when we move from a machine with an old version of Office to a machine with a new version of Office. I had to find all fo the methods and invoke nodes and reselect what was being accessed.

I wrote it off as being a change to the ActiveX implementation.

So if you had exactly the same version of the ActiveX driver installed on both machines... that issue should go away.

Ben