What is the best way to fix broken vis when the type library of the active x server changes (methods or properties addes)?

[richard.rochford]

Every time there is a change to the active X server I am developing drivers for I have to go back through all the vi's I have developed and re-point the methods an properties back to what they were to fix the broken arrows. The only change in the Active X server is usually an additional method or property. There has to be a better way, I have over 130 vi's I have to fix for every update and it keeps getting larger.

[JeanPierre]

Save the ActiveX refnum control as a typedef control and replace all occurences of your control by the typedef. When a change occurs, all you have to do is to relink the typedef to the ActiveX Server; the change will apply to all occurences of the typedef.

Jean-Pierre

[richard.rochford]

This is somthing I can try, but I don't think it will solve my problem. My reference never changes, it is always the same and is correctly registered with every new release. What does change are the number of methods and properties. With each new release there are usualy additional methods and properties; however, the old ones are still there with the same names (thank goodness). The problem this causes with LabVIEW, apparently, whenever there is a change in the type library you must re-point all the methods an properties again, at least this is what I am experiencing. If doing what you suggested works, it would be some kind of magic that I would like an explanation for.

[JeanPierre]

Sorry, I misunderstood your problem... I thought it was related to broken VIs due to modified ActiveX reference. It is always a good idea to typedef the ActiveX control but it might not solve your property node problem.

Jean-Pierre

[wiggle]

I am having the exact same problem as you have. Did you find out the better way for this yet?