R
rocheey
Im writing a database app which is to be run from an html form in a
local intranet.
Its an unsigned activex, and I believe Ive got all the security
settings tweaked: loading,scripting, Trusted zone, etc.
Im using VB6, have done a few of these before, and Im testing on
XP/win2k, running on IE6, and IE5 rspectively.
The first rev of the control loaded, self registered, displayed, etc,
in all browsers.
The next rev added child windows to the control, and I switched back to
DAO from ADO because of speed issues.
The control no longer loads,displays, or self registers. I upped the
rev, recompiled, and still no go.
I created a new activex from scratch, as a "new" control, and pasted
the old controls/code into it, and still no loading/self regsitering.
The first version will still load/self regsiter if I clean out the
target machines registry.
An activeX created from scratch, using child windows, but not much
else, will load/self register.
An ActiveX control created from scratch, using the default data
control, will -NOT- load/self register.
Im getting no errors, of course, because the control is not even making
it to the self-register phase, so the control is not getting loaded.
One interesting behaviour I noticed is that, despite kicking down
security to lowest level for testing, on both Intranet and Internet, I
get a toolbar type security warning on not loading the control *if I
load the page locally* .... If I click on the warning, however, and say
to allow scripting of the control, it still does not self regsiter. If
I load the page from the server, i get no such toolbar type warning,
and it still fails to self register.
I created an actual install for the control, like a 'normal' app, and
then the page loaded, on all machines, because obviously the local
install was registering the control.
What can be causing the control to no longer self register ? Yes, a
simple "Hello, World" type control still loads/self registers, but that
is useless in the real world. I have no idea how to track this problem
down.
Any Ideas ?
local intranet.
Its an unsigned activex, and I believe Ive got all the security
settings tweaked: loading,scripting, Trusted zone, etc.
Im using VB6, have done a few of these before, and Im testing on
XP/win2k, running on IE6, and IE5 rspectively.
The first rev of the control loaded, self registered, displayed, etc,
in all browsers.
The next rev added child windows to the control, and I switched back to
DAO from ADO because of speed issues.
The control no longer loads,displays, or self registers. I upped the
rev, recompiled, and still no go.
I created a new activex from scratch, as a "new" control, and pasted
the old controls/code into it, and still no loading/self regsitering.
The first version will still load/self regsiter if I clean out the
target machines registry.
An activeX created from scratch, using child windows, but not much
else, will load/self register.
An ActiveX control created from scratch, using the default data
control, will -NOT- load/self register.
Im getting no errors, of course, because the control is not even making
it to the self-register phase, so the control is not getting loaded.
One interesting behaviour I noticed is that, despite kicking down
security to lowest level for testing, on both Intranet and Internet, I
get a toolbar type security warning on not loading the control *if I
load the page locally* .... If I click on the warning, however, and say
to allow scripting of the control, it still does not self regsiter. If
I load the page from the server, i get no such toolbar type warning,
and it still fails to self register.
I created an actual install for the control, like a 'normal' app, and
then the page loaded, on all machines, because obviously the local
install was registering the control.
What can be causing the control to no longer self register ? Yes, a
simple "Hello, World" type control still loads/self registers, but that
is useless in the real world. I have no idea how to track this problem
down.
Any Ideas ?