MSFLXGRD.OCX and Error 747 'Design Time license' missing

  • Follow


Did MS Release a newer version of MSFLXGRD.OCX that breaks legacy VB6 
applications?  I'm getting this error suddenly:

'Run Time Error 747'
" No Design-time license information found for control 
'MSFlexGridLib.MSFlexGrid'...

I tried using the AddLicense but that failed since the ocx is already in a 
form/project.

Thank you for all suggestions. 

0
Reply bitpusher1010 12/9/2009 4:46:47 PM

"bitpusher1010" <info@convert-files.com> wrote in message
news:79CEBF76-BC8F-4F30-B5E6-C8FBD8E6A8E3@microsoft.com...
> Did MS Release a newer version of MSFLXGRD.OCX that breaks legacy VB6
> applications?  I'm getting this error suddenly:
>
> 'Run Time Error 747'
> " No Design-time license information found for control
> 'MSFlexGridLib.MSFlexGrid'...
>
> I tried using the AddLicense but that failed since the ocx is already in a
> form/project.
>
> Thank you for all suggestions.
>

Basically your licensing file got trashed.

Have your recently installed .Net? Anything else? Done some cleaning?

How long as it been since you cleaned the Registry?

-ralph



0
Reply Ralph 12/9/2009 5:36:46 PM


It is beginning to show up on my end users computers, not mine.  And it is 
happening at more than one location.

I install and register version 6.1.97.82 and my end users have version 
6.1.98.6. So, it appears they have a newer version of this component than I 
do in my development computer.

Thank you for any assistance, it is an urgent issue.


"Ralph" <nt_consulting64@yahoo.com> wrote in message 
news:uFchLaPeKHA.2184@TK2MSFTNGP04.phx.gbl...
>
> "bitpusher1010" <info@convert-files.com> wrote in message
> news:79CEBF76-BC8F-4F30-B5E6-C8FBD8E6A8E3@microsoft.com...
>> Did MS Release a newer version of MSFLXGRD.OCX that breaks legacy VB6
>> applications?  I'm getting this error suddenly:
>>
>> 'Run Time Error 747'
>> " No Design-time license information found for control
>> 'MSFlexGridLib.MSFlexGrid'...
>>
>> I tried using the AddLicense but that failed since the ocx is already in 
>> a
>> form/project.
>>
>> Thank you for all suggestions.
>>
>
> Basically your licensing file got trashed.
>
> Have your recently installed .Net? Anything else? Done some cleaning?
>
> How long as it been since you cleaned the Registry?
>
> -ralph
>
>
> 

0
Reply bitpusher1010 12/9/2009 6:56:48 PM

"bitpusher1010" <info@convert-files.com> wrote in message 
news:%23IzLfFQeKHA.1648@TK2MSFTNGP05.phx.gbl...
> It is beginning to show up on my end users computers, not mine.  And it is 
> happening at more than one location.
>
> I install and register version 6.1.97.82 and my end users have version 
> 6.1.98.6. So, it appears they have a newer version of this component than 
> I do in my development computer.

Do you mean 6.1.98.16? If so, it's part of the December 2008/May 2009(v2) 
Screwup update:

Description of the cumulative update rollup for the Visual Basic 6.0 Service 
Pack 6 Runtime Extended Files
http://support.microsoft.com/kb/957924


See the heading "List of fixes to issues discovered in December 2008 
Cumulative Update for Visual Basic 6.0 Service Pack 6 (SP6) Runtime Extended 
Files".

One of them talks about using Controls.Add, but I tested this with Winsock 
when placed on a form and using Load method, and it was working fine. I 
didn't test Controls.Add which is one of the things that the article talked 
about.


0
Reply Nobody 12/9/2009 9:49:35 PM

Sounds promising. So... Microsoft may have released OCX's that broke legacy 
VB6 applications... so it seems to me.

Thank you. 

0
Reply bitpusher1010 12/10/2009 2:40:45 AM

> Description of the cumulative update rollup for the Visual Basic 6.0 
> Service Pack 6 Runtime Extended Files
> http://support.microsoft.com/kb/957924

Sounds promising. So... Microsoft may have released OCX's that broke legacy
VB6 applications... so it seems to me.

Thank you very much. I'll give the new VB6 run times a try. 

1
Reply bitpusher1010 12/10/2009 2:43:35 AM

5 Replies
837 Views

(page loaded in 0.074 seconds)

Similiar Articles:
















7/20/2012 12:29:59 AM


Reply: