[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.vb.general.discussion

I have two different CLSIDs pointing to MS FlexGrid control

(Mike Mitchell)

3/10/2011 2:18:00 PM

In the registry (W2K) I find:

[HKEY_CLASSES_ROOT\CLSID\{74DD2713-BA98-4D10-A16E-270BBEB9B555}]
@="Microsoft FlexGrid Control, version 6.0 (SP6)"

and

[HKEY_CLASSES_ROOT\CLSID\{6262D3A0-531B-11CF-91F6-C2863C385E30}]
@="Microsoft FlexGrid Control, version 6.0 (SP6)"

Make My Manifest is getting confused and is including both refs. The
subsequent manifest won't work, unless I manually edit it and remove
the duplicate ref.

How did these two different CLSIDs materialise on my system?

MM
7 Answers

Mayayana

3/10/2011 2:24:00 PM

0

I entered the first CLSID into Google and found
the following. (Total time spent -- about 45 seconds):

http://www.vbmonster.com/Uwe/Forum.aspx/vb-controls/6153/new-MsFlxGrd-ocx-does-not-work-o...

The idea is that you ask help from others *after*
you've tried and failed to find the answer yourself.

(Mike Mitchell)

3/10/2011 3:50:00 PM

0

On Thu, 10 Mar 2011 09:23:53 -0500, "Mayayana"
<mayayana@invalid.nospam> wrote:

>I entered the first CLSID into Google and found
>the following. (Total time spent -- about 45 seconds):
>
>http://www.vbmonster.com/Uwe/Forum.aspx/vb-controls/6153/new-MsFlxGrd-ocx-does-not-work-o...
>
> The idea is that you ask help from others *after*
>you've tried and failed to find the answer yourself.

How do I fix my system, then? That web page doesn't say. And how did
my PC acquire two different CLSIDs? After all, I have only one actual
MSFlxGrd.ocx registered in system32.

MM

ralph

3/10/2011 6:31:00 PM

0

On Thu, 10 Mar 2011 15:49:32 +0000, MM <kylix_is@yahoo.co.uk> wrote:

>On Thu, 10 Mar 2011 09:23:53 -0500, "Mayayana"
><mayayana@invalid.nospam> wrote:
>
>>I entered the first CLSID into Google and found
>>the following. (Total time spent -- about 45 seconds):
>>
>>http://www.vbmonster.com/Uwe/Forum.aspx/vb-controls/6153/new-MsFlxGrd-ocx-does-not-work-o...
>>
>> The idea is that you ask help from others *after*
>>you've tried and failed to find the answer yourself.
>
>How do I fix my system, then? That web page doesn't say. And how did
>my PC acquire two different CLSIDs? After all, I have only one actual
>MSFlxGrd.ocx registered in system32.
>

MS updated the control. (The newer one starts 74DD2713...)

Besides modifying the internals of the component, principally security
issues (or rather that is about the only thing we were told <g>), the
interface was also modified and thus a new CLSID was required. The
physical component actually supports both Interfaces. Happens all the
time with ActiveX.

To lessen the impact on previous users of the original control they
left the description and AppID/ProgID the same. For single clients
this is rarely an issue.
(Well not entirely, as Mayayana's reply noted, MS has put the kibosh
on the original interface.)

However, in your case it is an issue. It is analogous to what would
happen if you try to reference both
"ActiveX Data Object Library 2.5", &
"ActiveX Data Object Library 2.8"
in the same project. Same component, unfortunately two different
interfaces.

You have both references because you likely installed the original VB6
and then installed SP6 (an/or perhaps even the updated v6 control kit,
or Office, or anything else) Like a lot of ActiveX components the
MSFlexGrid development and release cycle was not timed with that of VB
or other products.

The easiest "fix" for manifests is to simply delete the 6262D3A0...
CLSID. This would likely break any existing apps or utilities
configured to use early binding with the older version, but there
might not be that many. Personally, I'd probably just create a little
utility to 'repair' the Manifest.

-ralph

ralph

3/10/2011 6:35:00 PM

0

>
>The easiest "fix" for manifests is to simply delete the 6262D3A0...
>CLSID. This would likely break any existing apps or utilities
>configured to use early binding with the older version, but there
>might not be that many.

Meant to say ...
The easiest "fix" for manifests is to simply delete the 6262D3A0...
CLSID from the Registry.

-ralph

(Mike Mitchell)

3/10/2011 6:56:00 PM

0

On Thu, 10 Mar 2011 12:31:23 -0600, ralph <nt_consulting64@yahoo.net>
wrote:

>On Thu, 10 Mar 2011 15:49:32 +0000, MM <kylix_is@yahoo.co.uk> wrote:
>
>>On Thu, 10 Mar 2011 09:23:53 -0500, "Mayayana"
>><mayayana@invalid.nospam> wrote:
>>
>>>I entered the first CLSID into Google and found
>>>the following. (Total time spent -- about 45 seconds):
>>>
>>>http://www.vbmonster.com/Uwe/Forum.aspx/vb-controls/6153/new-MsFlxGrd-ocx-does-not-work-o...
>>>
>>> The idea is that you ask help from others *after*
>>>you've tried and failed to find the answer yourself.
>>
>>How do I fix my system, then? That web page doesn't say. And how did
>>my PC acquire two different CLSIDs? After all, I have only one actual
>>MSFlxGrd.ocx registered in system32.
>>
>
>MS updated the control. (The newer one starts 74DD2713...)
>
>Besides modifying the internals of the component, principally security
>issues (or rather that is about the only thing we were told <g>), the
>interface was also modified and thus a new CLSID was required. The
>physical component actually supports both Interfaces. Happens all the
>time with ActiveX.
>
>To lessen the impact on previous users of the original control they
>left the description and AppID/ProgID the same. For single clients
>this is rarely an issue.
>(Well not entirely, as Mayayana's reply noted, MS has put the kibosh
>on the original interface.)
>
>However, in your case it is an issue. It is analogous to what would
>happen if you try to reference both
> "ActiveX Data Object Library 2.5", &
> "ActiveX Data Object Library 2.8"
>in the same project. Same component, unfortunately two different
>interfaces.
>
>You have both references because you likely installed the original VB6
>and then installed SP6 (an/or perhaps even the updated v6 control kit,
>or Office, or anything else) Like a lot of ActiveX components the
>MSFlexGrid development and release cycle was not timed with that of VB
>or other products.
>
>The easiest "fix" for manifests is to simply delete the 6262D3A0...
>CLSID. This would likely break any existing apps or utilities
>configured to use early binding with the older version, but there
>might not be that many. Personally, I'd probably just create a little
>utility to 'repair' the Manifest.
>
>-ralph

Thanks. Yes, I installed VB6 afresh, then applied ALL the software
updates, including the cumulative update rollup (KB957924) .

MM

(Mike Mitchell)

3/10/2011 8:53:00 PM

0

On Thu, 10 Mar 2011 18:56:17 +0000, MM <kylix_is@yahoo.co.uk> wrote:

[snip]

I've just noticed that it is not just MsFlexGrid with two different
CLSIDs. the MCI control also screws up in the manifest!

<comClass clsid="{C1A8AF25-1257-101B-8FB0-0020AF039CA3}"
tlbid="{C1A8AF28-1257-101B-8FB0-0020AF039CA3}"
threadingModel="Apartment" progid="MCI.MMControl.1"
description="Microsoft Multimedia Control 6.0 (SP6)" />

<comClass clsid="{F65348F7-505D-4FAB-B66C-D76CFFC2BD78}"
tlbid="{C1A8AF28-1257-101B-8FB0-0020AF039CA3}"
threadingModel="Apartment" progid="MCI.MMControl.1"
description="Microsoft Multimedia Control 6.0 (SP6)" />

I deleted the first one above and then the .exe ran OK.

I suppose this is going to be a similar PITA for all the controls
"touched" (torched?) by the cumulative rollup thingy.

MM

(nobody)

3/10/2011 9:33:00 PM

0

"MM" <kylix_is@yahoo.co.uk> wrote in message
news:b7ein6htp2sgeudt4nln3revcaahouoic9@4ax.com...
> On Thu, 10 Mar 2011 18:56:17 +0000, MM <kylix_is@yahoo.co.uk> wrote:
>
> [snip]
>
> I've just noticed that it is not just MsFlexGrid with two different
> CLSIDs. the MCI control also screws up in the manifest!
>
> <comClass clsid="{C1A8AF25-1257-101B-8FB0-0020AF039CA3}"
> tlbid="{C1A8AF28-1257-101B-8FB0-0020AF039CA3}"
> threadingModel="Apartment" progid="MCI.MMControl.1"
> description="Microsoft Multimedia Control 6.0 (SP6)" />
>
> <comClass clsid="{F65348F7-505D-4FAB-B66C-D76CFFC2BD78}"
> tlbid="{C1A8AF28-1257-101B-8FB0-0020AF039CA3}"
> threadingModel="Apartment" progid="MCI.MMControl.1"
> description="Microsoft Multimedia Control 6.0 (SP6)" />
>
> I deleted the first one above and then the .exe ran OK.
>
> I suppose this is going to be a similar PITA for all the controls
> "touched" (torched?) by the cumulative rollup thingy.

I would open the VBP file in Notepad, which tells me the GUID that I am
actually using, then edit the manifest and remove the other GUID.