Hi,
You can access the ActiveX dll as a dll is stead of an automation component.
This is a bit more complicated to program (but just a bit, since the dll has
known prototypes), but will resolve the problem.
Btw. The general idea behind COM is to be backwards compatible, are you sure
there isn't a way to give the new component the same name as the old? I
think there should be a way in VB to set the registry key named
'VersionIndependentProgID' to define this name.
Hope it helps,
Wiebe.
"leebmic"
wrote in message
news:50650000000800000038480000-1019262487000@exchange.ni.com...
> Hello,
>
> we are using Visual Basic 6 to proramm an ActiveX DLL as middle tier
> Database Access Component. In Labview we made a LLB for Database
> Access usin
g the VB6 ActiveX Dll.
> Everytime we modify (add or change) the Interface of the ActiveX DLL
> and recompile it with VB6 we have to adjust the Automation Refnums in
> Labview in every SubVI.
> Is there an easier way to do this - or is it possible to automate this
> task ?
>
> Thanks for your help
>
> Michael