Prev: Detect Excel application minimize/restore?
Next: GDIPlus font size (from other post)
From: bitpusher1010 on 9 Dec 2009 11:46
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.

From: Ralph on 9 Dec 2009 12:36

"bitpusher1010" <info(a)convert-files.com> wrote in message
news:79CEBF76-BC8F-4F30-B5E6-C8FBD8E6A8E3(a)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



From: bitpusher1010 on 9 Dec 2009 13:56
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(a)yahoo.com> wrote in message
news:uFchLaPeKHA.2184(a)TK2MSFTNGP04.phx.gbl...
>
> "bitpusher1010" <info(a)convert-files.com> wrote in message
> news:79CEBF76-BC8F-4F30-B5E6-C8FBD8E6A8E3(a)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
>
>
>

From: Nobody on 9 Dec 2009 16:49
"bitpusher1010" <info(a)convert-files.com> wrote in message
news:%23IzLfFQeKHA.1648(a)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.


From: bitpusher1010 on 9 Dec 2009 21:40
Sounds promising. So... Microsoft may have released OCX's that broke legacy
VB6 applications... so it seems to me.

Thank you.

 |  Next  |  Last
Pages: 1 2
Prev: Detect Excel application minimize/restore?
Next: GDIPlus font size (from other post)