ActiveX control "Click to activate and use this control" message

For IE users, we now encountered a "Click to activate and use this control"
when the web page has an ActiveX Control.
There is a compatibility patch that changes the default bahavior back to
what it was prior to the April Security update, but it is only temporary.
In the following article
http://capitalhead.com/articles/click-to-activate-and-use-th is-control---kb912812.aspx,
it mentions that the workaround ultimately rests with the website designers
and how they implement the controls into your browser. How do we get around
it ?
Thank you very much.

Re: ActiveX control "Click to activate and use this control" message

fniles wrote:
> For IE users, we now encountered a "Click to activate and use this
> control" when the web page has an ActiveX Control.
>
> How do we get around it ?

http://msdn.microsoft.com/ieupdate/
http://msdn.microsoft.com/workshop/author/dhtml/overview/act ivating_activex.asp

--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925

Re: ActiveX control "Click to activate and use this control" message

It could turn out a blessing.

Not that Igor would not know hwo to write a nice atl component,
but arriving at a page I (that is other than from pigs) like to be suprised
intuitively
on what to do or what would happen, without being pushed into deactivating
all but
plain html rendering.


"fniles" wrote in message
news:%23bGJN8$OHHA.1248@TK2MSFTNGP02.phx.gbl...
> For IE users, we now encountered a "Click to activate and use this
control"
> when the web page has an ActiveX Control.
> There is a compatibility patch that changes the default bahavior back to
> what it was prior to the April Security update, but it is only temporary.
> In the following article
>
http://capitalhead.com/articles/click-to-activate-and-use-th is-control---kb912812.aspx,
> it mentions that the workaround ultimately rests with the website
designers
> and how they implement the controls into your browser. How do we get
around
> it ?
> Thank you very much.
>
>