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

[fniles]

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
[url]http://capitalhead.com/articles/click-to-activate-and-use-this-control---kb912812.aspx[/url],
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.

[Igor Tandetnik]

fniles <fniles@pfmail.com> 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 ?

[url]http://msdn.microsoft.com/ieupdate/[/url]
[url]http://msdn.microsoft.com/workshop/author/dhtml/overview/activating_activex.asp[/url]

--
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

[asdf]

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" <fniles@pfmail.com> 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
>

[url]http://capitalhead.com/articles/click-to-activate-and-use-this-control---kb912812.aspx[/url],

> 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.
>
>