I've created an ActiveX control that will be displayed within IE. I have all
the security settings in IE on each machine I've tested on setup to allow
the display of the control. The control will display just fine on the
development machine. When I attempt to display the control on the other
systems I simply receive a blank page w/the image placeholder. After some
effort diagnosing the issue I've discovered that if I include the VB6
runtime & OLE files in the CAB file it works on all machines that I test it
on. But if I select the option of not including the files and instead select
to download the files from MS it fails.
I'm using VB6 SP6 w/the Package & Deployment wizard.
Is anyone familiar with this issue? Is there some workaround to it or
something that I'm just not doing to make this work right? I especially
dislike needing to include the VB6 files in the CAB file as, of course, the
CAB is much larger and once the VB6 files have been installed a reboot is
always requested even when its not needed.
Thanks in advance!
JW
Gaurav - http://www.gauravcreations.com - 10 Oct 2004 11:56 GMT
i hope you don't forget to include your control with the setup . :)
nyways wat if you manually register your control on a machine with the
runtimes already installed..
also try this.... install without the runtimes etc. . and if it does not run
then install only the runtimes on that m/c.. see if it runs...
> I've created an ActiveX control that will be displayed within IE. I have all
> the security settings in IE on each machine I've tested on setup to allow
[quoted text clipped - 17 lines]
>
> JW
Jerry West - 11 Oct 2004 02:14 GMT
Thank you for the response. Yes, I have included the OCX in the setup.
I tried the first suggestion of manually registering the OCX on a machine
where the VB runtimes were already installed. This worked. As soon as the
OCX was manually registered via RegSvr32 and I refreshed the browser and the
control was then present on the page.
I tried again on a system that was perfectly clean --a fresh install of NT4
SP6. It did include a copy of MSVBVM60..DLL that was from the original VB6
release. My control uses VB SP6. So I knew it would have to download and
install a fresh copy of the runtime. I then accessed the web page that
installs and displays the control. It failed as before. I then searched for
the OCX thinking I should find it in the system32 folder but it wasn't
there. I then looked at the VB runtime and found it to still be the old
version. I know the CAB file downloaded because I was prompted as to whether
or not I wanted to install it after the download. I then copied over the OCX
and manually registered it. When completed I refreshed the page. The control
then appeared.
So it appears nothing gets installed and registered. I've looked over the
INF from the setup routine and it looks fine. What could I possibly be
missing here?
JW
>i hope you don't forget to include your control with the setup . :)
> nyways wat if you manually register your control on a machine with the
[quoted text clipped - 29 lines]
>>
>> JW
Gaurav - http://www.gauravcreations.com - 11 Oct 2004 09:43 GMT
try using a third party setup generator .. and see what happens....
use PDW got get a list of all dependent files and then include them in the
3rd party tool.. leave the vb runtimes ...
--
Gaurav Creations
> Thank you for the response. Yes, I have included the OCX in the setup.
>
[quoted text clipped - 54 lines]
> >>
> >> JW
Jerry West - 14 Oct 2004 06:39 GMT
I have finally resolved this issue. As it turns out, it was a Microsoft bug.
The following KB document details the issue: Q254166
JW
> I've created an ActiveX control that will be displayed within IE. I have
> all the security settings in IE on each machine I've tested on setup to
[quoted text clipped - 17 lines]
>
> JW