Re: Problem with ActiveXObject and <OBJECT> ...
- From: mr_unreliable <kindlyReplyToNewsgroup@xxxxxxxxxxx>
- Date: Mon, 18 Sep 2006 12:28:11 -0400
Duncan, as you suggest, it may be a security issue.
The usual response to a security issue is to set your browser
to the lowest security setting, but I'm not sure how this
applies in a server environment.
The only other thought I had was my own troubles instantiating
objects, which are present in the registry, but which
microsoft doesn't want me using. As best I can tell,
ms is looking around for "siting" interfaces which I
am not providing. For example, ms is not allowing me
to instantiate the vbScript dll (object), most likely
because I am not providing the wscript interfaces.
But then, since you wrote the ocx yourself, you are not
building in those requirements.
As you probably know, an ocx is looking for siting interfaces,
but the browser (at least IE) does provide them, as does
your normal vb Form object.
I'm stumped, jw
DuncanH wrote:
Hi jw,.
Yep, I've looked at the registry values, it's there and registered
correctly. I've also compared the registry entries for the control that
does not work with one created in the same manner, but works. I cannot
see any differences between them.
- Follow-Ups:
- Re: Problem with ActiveXObject and <OBJECT> ...
- From: DuncanH
- Re: Problem with ActiveXObject and <OBJECT> ...
- References:
- Problem with ActiveXObject and <OBJECT> ...
- From: DuncanH
- Re: Problem with ActiveXObject and <OBJECT> ...
- From: mr_unreliable
- Re: Problem with ActiveXObject and <OBJECT> ...
- From: DuncanH
- Problem with ActiveXObject and <OBJECT> ...
- Prev by Date: Re: vbs to exe
- Next by Date: Re: Where to start
- Previous by thread: Re: Problem with ActiveXObject and <OBJECT> ...
- Next by thread: Re: Problem with ActiveXObject and <OBJECT> ...
- Index(es):
Relevant Pages
|