Enterprise Client Community

Hello,

we are using three different ActiveX controls in our application and we have to know if this ActiveX contorls are installed on the system or not.

The first solution was to integrate 'mini ActiveXe' on the startpage to see if we get a response from the ActiveX. But this solution is slow and we could get in trouble if we have the same ActiveX initialized twice.

Another solution from our side could be to develop a fourth ActiveX which tests if the other three ActiveX exists.

But maybe it is a better solution if the Enterprise Client can test if a ActiveX exists without initializing the ActiveX.

Thanks,
Ralph

Hi Ralph,

the only way to test if an ACTIVEX component is available on client side for us is to create an instance for it.
So, the best way to test is, what you propose: write an own ACTIVEX component for this test. This makes the result available via ActivrX-properties, that themselves are sent (via PROPERTYINTEREST) to the server processing. The decision on server side then is:

(.) nothing is coming ==> event the check-ACtiveX component is not available
(.) something is coming ==> ok, then all info is inside your hands

Björn