Activex "click to activate" work round does not work intermittentl

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I work on a website that includes several activeX controls. After the April
update that made IE comply with Eolas we changed the code that includes the
controls. Rather than embedding the <object> tags in the pages we insert
them using JScript in an included .js file.

The embedded code looks like this:
<div id="DivDateTime"></div>
<script language="JScript">
CreateControl( 'DivDateTime','<OBJECT id="DTP"
codeBase="../Packages/DateTime.CAB#version=123" classid="CLSID:xxxx"
VIEWASTEXT><PARAM NAME="foo" VALUE="bar><SPAN STYLE="COLOR:red">ActiveX
control [DateTime] failed to load </SPAN></OBJECT>');
</script>

and the included js file just contains one function:
function CreateControl(ElementId, innerHTML)
{
var d = document.getElementById(ElementId);
d.innerHTML = innerHTML;
}

This solution works 99% of the time, but intermittently we still get the
tooltip saying "click to activate etc." As far as I can tell we have
followed MS advice on resolving the issue but sometimes even that does not
work - any ideas why this may be?
 
Thanks Jon, I'd already read that page a few times but it seems to have been
updated since I last looked - unfortunately there's nothing that points to
the behaviour I'm experiencing.

I have used the MS suggested work-round, and it seems to work for the
majority of the time, but every now and then IE will decide that I need to
click on every ActiveX control to activate before I can use it. A refresh of
the page doesn't seem to resolve the issue, but closing IE and opening it
again does. Any other ideas?

Jon Kennedy said:
See the More Information/Known Issues section of this article for possible
help:

Internet Explorer ActiveX update
http://support.microsoft.com/kb/912945/en-us

More info:
http://msdn.microsoft.com/library/d.../author/dhtml/overview/activating_activex.asp

--

Jon R. Kennedy MS MVP/IE
Charlotte, NC USA
(e-mail address removed)


MarkD said:
I work on a website that includes several activeX controls. After the
April
update that made IE comply with Eolas we changed the code that includes
the
controls. Rather than embedding the <object> tags in the pages we insert
them using JScript in an included .js file.

The embedded code looks like this:
<div id="DivDateTime"></div>
<script language="JScript">
CreateControl( 'DivDateTime','<OBJECT id="DTP"
codeBase="../Packages/DateTime.CAB#version=123" classid="CLSID:xxxx"
VIEWASTEXT><PARAM NAME="foo" VALUE="bar><SPAN STYLE="COLOR:red">ActiveX
control [DateTime] failed to load </SPAN></OBJECT>');
</script>

and the included js file just contains one function:
function CreateControl(ElementId, innerHTML)
{
var d = document.getElementById(ElementId);
d.innerHTML = innerHTML;
}

This solution works 99% of the time, but intermittently we still get the
tooltip saying "click to activate etc." As far as I can tell we have
followed MS advice on resolving the issue but sometimes even that does not
work - any ideas why this may be?
 
Thanks for the offer Viktor, but this is an intranet solution and not one
that I copuld make available on the internet due to copyright restrictions.

It certainly looks like an IE bug, it affects all activeX controls on the
page when it does occur. I will be reporting this to Microsoft, but I was
hoping that someone else may have come acrosss it and found the solution
already.
 
I wonder if the problem may be associated with the browser pulling all or
part of the page in question out of the cache (TIF). Clicking the Refresh
button doesn't always to the trick of reloading the page from the original
source. Try a CTRL+F5. If this helps, then adjust IE's cache setting at
Tools...Internet Options...General tab, Settings button to "Every
visit....".
 
Thanks Jon, but I regularly clear my TIFand I always have the check for new
version every visit setting turned on. I can only assume that this is caused
by a bug in IE - it seems to treat the dynamically generated html as being
in-line. Could there be a race condition maybe? If the JScript that inserts
the innerHTML of the div completes before the OnLoad event of the page for
example?
 
I am running into a similar problem. I am using JScript to write the object
tags. It works fine when we tested internally. When we rolled it out to the
public, the control failed to load. The particular webpage we are using
contains several ActiveX controls. They all load except for one. Internally
the controls work fine. Externally, all but one loads. All these controls
were working before the latest patch to IE. Any idea what would cause this?

Thanks.
 
This is still an issue for us. We've instructed our clients to install the
"backwards compatibility" patch. But, this patch expires in June. This is
turning into a big issue here at my company. Can you give me any insight to
this problem? Are you guys working on it? Perhaps, the expiration date for
the "backwards compatibility" patch can be extended a few months until these
issues are ironed out.
Jon Kennedy said:
See the More Information/Known Issues section of this article for possible
help:

Internet Explorer ActiveX update
http://support.microsoft.com/kb/912945/en-us

More info:
http://msdn.microsoft.com/library/d.../author/dhtml/overview/activating_activex.asp

--

Jon R. Kennedy MS MVP/IE
Charlotte, NC USA
(e-mail address removed)


MarkD said:
I work on a website that includes several activeX controls. After the
April
update that made IE comply with Eolas we changed the code that includes
the
controls. Rather than embedding the <object> tags in the pages we insert
them using JScript in an included .js file.

The embedded code looks like this:
<div id="DivDateTime"></div>
<script language="JScript">
CreateControl( 'DivDateTime','<OBJECT id="DTP"
codeBase="../Packages/DateTime.CAB#version=123" classid="CLSID:xxxx"
VIEWASTEXT><PARAM NAME="foo" VALUE="bar><SPAN STYLE="COLOR:red">ActiveX
control [DateTime] failed to load </SPAN></OBJECT>');
</script>

and the included js file just contains one function:
function CreateControl(ElementId, innerHTML)
{
var d = document.getElementById(ElementId);
d.innerHTML = innerHTML;
}

This solution works 99% of the time, but intermittently we still get the
tooltip saying "click to activate etc." As far as I can tell we have
followed MS advice on resolving the issue but sometimes even that does not
work - any ideas why this may be?
 
JohnR, are you experiencing the same symptom as me (where the activeX control
requires a click to activate very intermittently), or is it a case of one
control never loading?

JohnR said:
This is still an issue for us. We've instructed our clients to install the
"backwards compatibility" patch. But, this patch expires in June. This is
turning into a big issue here at my company. Can you give me any insight to
this problem? Are you guys working on it? Perhaps, the expiration date for
the "backwards compatibility" patch can be extended a few months until these
issues are ironed out.
Jon Kennedy said:
See the More Information/Known Issues section of this article for possible
help:

Internet Explorer ActiveX update
http://support.microsoft.com/kb/912945/en-us

More info:
http://msdn.microsoft.com/library/d.../author/dhtml/overview/activating_activex.asp

--

Jon R. Kennedy MS MVP/IE
Charlotte, NC USA
(e-mail address removed)


MarkD said:
I work on a website that includes several activeX controls. After the
April
update that made IE comply with Eolas we changed the code that includes
the
controls. Rather than embedding the <object> tags in the pages we insert
them using JScript in an included .js file.

The embedded code looks like this:
<div id="DivDateTime"></div>
<script language="JScript">
CreateControl( 'DivDateTime','<OBJECT id="DTP"
codeBase="../Packages/DateTime.CAB#version=123" classid="CLSID:xxxx"
VIEWASTEXT><PARAM NAME="foo" VALUE="bar><SPAN STYLE="COLOR:red">ActiveX
control [DateTime] failed to load </SPAN></OBJECT>');
</script>

and the included js file just contains one function:
function CreateControl(ElementId, innerHTML)
{
var d = document.getElementById(ElementId);
d.innerHTML = innerHTML;
}

This solution works 99% of the time, but intermittently we still get the
tooltip saying "click to activate etc." As far as I can tell we have
followed MS advice on resolving the issue but sometimes even that does not
work - any ideas why this may be?
 
The control does not load. Users see a red X. The only that has changed in
our code is the way the control is loaded. Instead of embedding it into the
html, I am calling a javascript method to write in the object. This works for
other controls on the page. Even this control loads when accessed internally.
For some reason, users outside the company are having problems.

MarkD said:
JohnR, are you experiencing the same symptom as me (where the activeX control
requires a click to activate very intermittently), or is it a case of one
control never loading?

JohnR said:
This is still an issue for us. We've instructed our clients to install the
"backwards compatibility" patch. But, this patch expires in June. This is
turning into a big issue here at my company. Can you give me any insight to
this problem? Are you guys working on it? Perhaps, the expiration date for
the "backwards compatibility" patch can be extended a few months until these
issues are ironed out.
Jon Kennedy said:
See the More Information/Known Issues section of this article for possible
help:

Internet Explorer ActiveX update
http://support.microsoft.com/kb/912945/en-us

More info:
http://msdn.microsoft.com/library/d.../author/dhtml/overview/activating_activex.asp

--

Jon R. Kennedy MS MVP/IE
Charlotte, NC USA
(e-mail address removed)


I work on a website that includes several activeX controls. After the
April
update that made IE comply with Eolas we changed the code that includes
the
controls. Rather than embedding the <object> tags in the pages we insert
them using JScript in an included .js file.

The embedded code looks like this:
<div id="DivDateTime"></div>
<script language="JScript">
CreateControl( 'DivDateTime','<OBJECT id="DTP"
codeBase="../Packages/DateTime.CAB#version=123" classid="CLSID:xxxx"
VIEWASTEXT><PARAM NAME="foo" VALUE="bar><SPAN STYLE="COLOR:red">ActiveX
control [DateTime] failed to load </SPAN></OBJECT>');
</script>

and the included js file just contains one function:
function CreateControl(ElementId, innerHTML)
{
var d = document.getElementById(ElementId);
d.innerHTML = innerHTML;
}

This solution works 99% of the time, but intermittently we still get the
tooltip saying "click to activate etc." As far as I can tell we have
followed MS advice on resolving the issue but sometimes even that does not
work - any ideas why this may be?
 
JohnR this is different from the problem I am experiencing - my problem is
very intermittent, the controls always load, but are sometimes not activated
automatically - it sounds like your problem is unrelated - possibly due to to
special characters breaking the javascript, if you post the URL here (or in a
separate post, as this is a separate problem) I could have a look at it for
you.

JohnR said:
The control does not load. Users see a red X. The only that has changed in
our code is the way the control is loaded. Instead of embedding it into the
html, I am calling a javascript method to write in the object. This works for
other controls on the page. Even this control loads when accessed internally.
For some reason, users outside the company are having problems.

MarkD said:
JohnR, are you experiencing the same symptom as me (where the activeX control
requires a click to activate very intermittently), or is it a case of one
control never loading?

JohnR said:
This is still an issue for us. We've instructed our clients to install the
"backwards compatibility" patch. But, this patch expires in June. This is
turning into a big issue here at my company. Can you give me any insight to
this problem? Are you guys working on it? Perhaps, the expiration date for
the "backwards compatibility" patch can be extended a few months until these
issues are ironed out.
:

See the More Information/Known Issues section of this article for possible
help:

Internet Explorer ActiveX update
http://support.microsoft.com/kb/912945/en-us

More info:
http://msdn.microsoft.com/library/d.../author/dhtml/overview/activating_activex.asp

--

Jon R. Kennedy MS MVP/IE
Charlotte, NC USA
(e-mail address removed)


I work on a website that includes several activeX controls. After the
April
update that made IE comply with Eolas we changed the code that includes
the
controls. Rather than embedding the <object> tags in the pages we insert
them using JScript in an included .js file.

The embedded code looks like this:
<div id="DivDateTime"></div>
<script language="JScript">
CreateControl( 'DivDateTime','<OBJECT id="DTP"
codeBase="../Packages/DateTime.CAB#version=123" classid="CLSID:xxxx"
VIEWASTEXT><PARAM NAME="foo" VALUE="bar><SPAN STYLE="COLOR:red">ActiveX
control [DateTime] failed to load </SPAN></OBJECT>');
</script>

and the included js file just contains one function:
function CreateControl(ElementId, innerHTML)
{
var d = document.getElementById(ElementId);
d.innerHTML = innerHTML;
}

This solution works 99% of the time, but intermittently we still get the
tooltip saying "click to activate etc." As far as I can tell we have
followed MS advice on resolving the issue but sometimes even that does not
work - any ideas why this may be?
 
I can't post the link since it requires login and navigating to various
pages. Do you think special characters in javascript would allow the control
to load when accessed internally and not externally?

MarkD said:
JohnR this is different from the problem I am experiencing - my problem is
very intermittent, the controls always load, but are sometimes not activated
automatically - it sounds like your problem is unrelated - possibly due to to
special characters breaking the javascript, if you post the URL here (or in a
separate post, as this is a separate problem) I could have a look at it for
you.

JohnR said:
The control does not load. Users see a red X. The only that has changed in
our code is the way the control is loaded. Instead of embedding it into the
html, I am calling a javascript method to write in the object. This works for
other controls on the page. Even this control loads when accessed internally.
For some reason, users outside the company are having problems.

MarkD said:
JohnR, are you experiencing the same symptom as me (where the activeX control
requires a click to activate very intermittently), or is it a case of one
control never loading?

:

This is still an issue for us. We've instructed our clients to install the
"backwards compatibility" patch. But, this patch expires in June. This is
turning into a big issue here at my company. Can you give me any insight to
this problem? Are you guys working on it? Perhaps, the expiration date for
the "backwards compatibility" patch can be extended a few months until these
issues are ironed out.
:

See the More Information/Known Issues section of this article for possible
help:

Internet Explorer ActiveX update
http://support.microsoft.com/kb/912945/en-us

More info:
http://msdn.microsoft.com/library/d.../author/dhtml/overview/activating_activex.asp

--

Jon R. Kennedy MS MVP/IE
Charlotte, NC USA
(e-mail address removed)


I work on a website that includes several activeX controls. After the
April
update that made IE comply with Eolas we changed the code that includes
the
controls. Rather than embedding the <object> tags in the pages we insert
them using JScript in an included .js file.

The embedded code looks like this:
<div id="DivDateTime"></div>
<script language="JScript">
CreateControl( 'DivDateTime','<OBJECT id="DTP"
codeBase="../Packages/DateTime.CAB#version=123" classid="CLSID:xxxx"
VIEWASTEXT><PARAM NAME="foo" VALUE="bar><SPAN STYLE="COLOR:red">ActiveX
control [DateTime] failed to load </SPAN></OBJECT>');
</script>

and the included js file just contains one function:
function CreateControl(ElementId, innerHTML)
{
var d = document.getElementById(ElementId);
d.innerHTML = innerHTML;
}

This solution works 99% of the time, but intermittently we still get the
tooltip saying "click to activate etc." As far as I can tell we have
followed MS advice on resolving the issue but sometimes even that does not
work - any ideas why this may be?
 
Back
Top