A possible solution that hasn't yet been addressed:
I am going to assume that there are two reasons that you could be using ActiveX. My second reason is what I want to lean towards:
First, you have to communicate with an outside application in Windows
Second, you aren't familiar enough with labview yet, and instead, have rewritten the code in VB and built it as an ActiveX Control.
Of course, there's probably another reason.....
If the reason is that you aren't yet familiar with LabVIEW, I would say that this is the perfect opportunity to learn. Give it a shot in LabVIEW. If you need help, say so.
Also, this is something you can try. I was able to get OCXs to update automatically, but there is a neat little trick to it. First,
DO NOT REGISTER the ocx. Instead, just put it in a folder somewhere in your directory hierarchy (you DO have a directory hierarchy, don't you?). Then, create a new container, or using the old one, navigate directly to the OCX from the container browser. You have to hit two different browse buttons to do this.
This should handle everything, even if you add new properties. I don't know for sure about methods. The project I worked on had ActiveX interface to an Access Database (we eventually replaced all of that *explative* code with real LabVIEW SQL code...much easier, better, more reliable, etc...) I had the programmer add some queries to the OCX, but I believe that these were only properties (data), but I can't be sure. My knowledge of ActiveX back then was a bit rusty.
Give those thigs a shot, and start programming in LabVIEW, instead of VB. You'll thank me later, I promise.
