Microsoft Office Access doesn't support this ActiveX control

  • Thread starter Thread starter swas
  • Start date Start date
S

swas

Hello,

I have an Access db with the MS Grid Control on one form. The program has
worked fine for 12M+ and I have done no changes.

On my home laptop I started getting the error 438, "Object doesn't support
this property or method" when opening the form.

Then the same thing at work.

I have tried re-setting all references to no avail.

I tried creating a new db, and if I try and place the control I get the
"Microsoft Office Access doesn't support this ActiveX control" error.

The only common thread between work and laptop is a Windows Update that
recently installed. Laptop is Office 2007, work is 2003.

Any help is really appreciated. It is a primary form I use daily in my
business!


Thanks in advance.


swas
 
Peter,

How are you?

Your reply seems right on the money, but I am still having problems.

On my laptop, with vb6 installed, I did the SP6 upgrade. The ocx gets
upgraded to a later version, but Access won't allow use saying "Microsoft
Office Access doesn't support this ActiveX control" still.

I tried the alternate solution link you provided (www.solutionsplus...)
which installs OK but I get a "Not licenced to use..." error.

Yes it is a Flex Grid (Or Heiracial Flex Grid, either would do) I'm using.

Any further help appreciated - I am barely an Access programmer, let alone
VB6.

The MS links add more confusion unfortunately...


Thanks in advance


swas
 
Thanks for that.

They are the same links as Peters, but makes it clear the runtime update is
needed as well!

I had done this on my work pc without vb6 which of course didn't work.
Laptop with vb6 I only installed the first update.

Thanks for the help.


swas



AccessVandal via AccessMonster.com said:
Here's a previous thread from mcnews. look at bottom link for updates.
------------------------------------------------------------------------------
------------------------------
The KB960715 "security update" sets a "kill bit" in the registry entry
for
several ActiveX controls, including several of MS's own VB6 controls.
MSFlexGrid and WinSock are two of those affected.
More info here:
<http://www.microsoft.com/technet/security/advisory/960715.mspx>

It turns out that there is another KB (957924) which updates those VB6
ActiveX controls to a later version which does not have the
vulnerability
and are therefore not kill-bitted. The "OK" version for msflxgrd.ocx
and
mswinsck.ocx 6.1.98.12.
You can download this VB6 update from here:
<http://support.microsoft.com/kb/957924>
------------------------------------------------------------------------------
----------------------------
swas said:
Peter,

How are you?

Your reply seems right on the money, but I am still having problems.

On my laptop, with vb6 installed, I did the SP6 upgrade. The ocx gets
upgraded to a later version, but Access won't allow use saying "Microsoft
Office Access doesn't support this ActiveX control" still.

I tried the alternate solution link you provided (www.solutionsplus...)
which installs OK but I get a "Not licenced to use..." error.

Yes it is a Flex Grid (Or Heiracial Flex Grid, either would do) I'm using.

Any further help appreciated - I am barely an Access programmer, let alone
VB6.

The MS links add more confusion unfortunately...

Thanks in advance

swas
It is due to a Windows Security update. Have a look at :-
http://support.microsoft.com/kb/957924
Click to expand...
[quoted text clipped - 7 lines]
Peter Hibbs.
Click to expand...
Click to expand...
Click to expand...
 
Did you re-register the Flex Grid controls with regsvr32.exe?

Peter Hibbs.

Thanks for that.

They are the same links as Peters, but makes it clear the runtime update is
needed as well!

I had done this on my work pc without vb6 which of course didn't work.
Laptop with vb6 I only installed the first update.

Thanks for the help.


swas



AccessVandal via AccessMonster.com said:
Here's a previous thread from mcnews. look at bottom link for updates.
------------------------------------------------------------------------------
------------------------------
The KB960715 "security update" sets a "kill bit" in the registry entry
for
several ActiveX controls, including several of MS's own VB6 controls.
MSFlexGrid and WinSock are two of those affected.
More info here:
<http://www.microsoft.com/technet/security/advisory/960715.mspx>

It turns out that there is another KB (957924) which updates those VB6
ActiveX controls to a later version which does not have the
vulnerability
and are therefore not kill-bitted. The "OK" version for msflxgrd.ocx
and
mswinsck.ocx 6.1.98.12.
You can download this VB6 update from here:
<http://support.microsoft.com/kb/957924>
------------------------------------------------------------------------------
----------------------------
swas said:
Peter,

How are you?

Your reply seems right on the money, but I am still having problems.

On my laptop, with vb6 installed, I did the SP6 upgrade. The ocx gets
upgraded to a later version, but Access won't allow use saying "Microsoft
Office Access doesn't support this ActiveX control" still.

I tried the alternate solution link you provided (www.solutionsplus...)
which installs OK but I get a "Not licenced to use..." error.

Yes it is a Flex Grid (Or Heiracial Flex Grid, either would do) I'm using.

Any further help appreciated - I am barely an Access programmer, let alone
VB6.

The MS links add more confusion unfortunately...

Thanks in advance

swas

It is due to a Windows Security update. Have a look at :-
http://support.microsoft.com/kb/957924
[quoted text clipped - 7 lines]

Peter Hibbs.
Click to expand...
Click to expand...
Click to expand...
 
I have a similar problem (the WinSock control in my case) and the responses below are helpful up to a point. But, I have VB 6.5 installed, not 6.0, and the fix <http://support.microsoft.com/kb/957924> refuses to install.

Note: my VB Help About panel shows "VBA: Retail 6.5.1053".

I did the original installation from genuine Microsoft CDs, labelled Office XP developer tools, 2001. The PC now giving me problems is also Windows XP, but with Access 2003. Any ideas please?
 
Back
Top