Re: ActiveX Download Conflict Directory

From: James Bond (bondshah700_at_hotmail.com)
Date: 03/24/04 

Date: 24 Mar 2004 14:25:05 -0800

Thanks a lot Randy,
I do have property set to Binary. It seems that whenever Class ID
changes for the same named OCX or packaged files, it creates CONFLICT
directory. If the class Id remains same, it just updates version
number. Version number doesn't seem to be a big problem. In my case,
we don't expect various levels of users to do anything.

I need either of these
1. Keep the class ID same, when I make any change to my code and
package all files together in CAB file.
2. When I push down the updated CAB/OCX, it needs to replace itself
regardless, what the old version is.

I am so screwed.
Any one ???

James

"Randy Birch" <rgb_removethis@mvps.org> wrote in message news:<eTNPlTTEEHA.1452@TK2MSFTNGP09.phx.gbl>...
> Outside my scope of expertise, but I suspect the problem is the binary
> compatibility of the ocx, such that the attempt to install the second
> version fails due to the fact the first was already downloaded and is
> registered on the user's system. Similar OCXs can be installed on the same
> machine as long as they are in different folders. In order to overwrite the
> existing control and update the control (rather than install a second, newer
> version), your user must either first unregister the first control, or you
> must set the compatibility mode to 'Binary' rather than the default
> 'Project' setting on the project property dialog under
> Project>Properties>Component.
>
> --
>
> Randy Birch
> MVP Visual Basic
> http://vbnet.mvps.org/
> Please respond only to the newsgroups so all can benefit.
>
>
> "James Bond" <bondshah700@hotmail.com> wrote in message
> news:f61fbd6f.0403231402.729d7499@posting.google.com...
> : Hello Randy,
> : I came across a typical error, which I am not sure, what other news
> : groups to post to, so please forgive me.
> :
> : I have a VB 6.0 exe and some other files in a CAB file which is
> : downloaded on client machines by ASP. Until now, I used default PDW
> : generated HTM code for version and codebase and it worked fine. Last
> : week, I need to make one small change to executable and I increased
> : the revision to 1. Before my OBJECT Tag looked like this
> : CLASSID="CLSID:0E3E7892-1E59-49E2-A8DB-CEAA80F959FC"
> : CODEBASE="CABS/SomeFile.CAB#version=1,0,0,0" Style="display:none"
> : now it looks like
> :
> : CLASSID="CLSID:28F0ADDA-2E99-4F46-AC50-EE3C852375A6"
> : CODEBASE="CABS/SomeFile.CAB#version=1,0,0,1" Style="display:none"
> : And now on client machines it fails. When I debugged on test machine,
> : i saw that it creates a CONFLICT.1 folder. I researched on microsoft
> : KB and found this article (
> : http://support.microsoft.com/default.aspx?scid=kb;en-us;196150 ),
> : according to which I have same name but class ID is different. So in
> : Winnt\Downloaded Program Files\ I see both these instances of my
> : control, original one with INSTALLED status where as the latest one
> : with DAMAGED status and thus my entire program fails.
> :
> : I understand the concept of CONFLICT folders, but at the same time, I
> : have to keep the names of the file same and PDW is going to generate
> : new Class ID everytime. So my question is "How would I prevent this
> : from happening on client machine and update the existing control with
> : the new one?"
> :
> : I would really appreciate any help.
> : Regards,
> : James

Relevant Pages

  • Re: ActiveX control doesnt display in IE
    ... I have included the OCX in the setup. ... I tried the first suggestion of manually registering the OCX on a machine ... I tried again on a system that was perfectly clean --a fresh install of NT4 ... My control uses VB SP6. ...
    (microsoft.public.vb.general.discussion)
  • Re: ActiveX control doesnt display in IE
    ... I have included the OCX in the setup. ... I tried the first suggestion of manually registering the OCX on a machine ... I tried again on a system that was perfectly clean --a fresh install of NT4 ... My control uses VB SP6. ...
    (microsoft.public.vb.controls.internet)
  • Re: ATL 7.0 Portability Issue
    ... OCX control onto a Jump ... If I run it on Windows XP SP2 it says that it registered OK, ... >> Everything works fine on Windows XP machine, but I can't even install it ...
    (microsoft.public.vc.mfc)
  • Re: ActiveX
    ... existing control and update the control (rather than install a second, ... downloaded on client machines by ASP. ... And now on client machines it fails. ...
    (microsoft.public.vb.controls.internet)
  • Re: Storing an OCX in a table then registering it
    ... So if your end user does not have rights to register ... > reference set to the control in your app, but if it isn't installed your app ... > install the OCX. ... The OCX needs to be installed by a proper installer ...
    (microsoft.public.access.formscoding)
Quantcast