Microsoft Office Access doesn't support this activeX control

[tkosel]

I have a database that contains some Microsoft Communication Controls. I
used these ActiveX controls to interface to a serial device quite some time
ago and it has been working fine. The active X control is registered to
"C:\WINDOWS\system32\MSCOMM32.OCX"

All of the sudden, they all stopped working. Access tells me there is no
object in this control when I try to design the form the control is on.

If I open a new db and try to insert that activeX control, Access tells me
that "Microsoft Office Access doesn't support this activeX control". What
has happened, any ideas on what caused it and how I can fix it?

 

[Tom van Stiphout]

On Mon, 14 Sep 2009 06:49:02 -0700, tkosel

Search the MSFT knowledge base for "killbits":
http://search.microsoft.com/Results.aspx?q=killbits

-Tom.
Microsoft Access MVP

 

[tkosel]

Tom,

In looking at your response, I assume you are saying that I don't have a
security update from Microsoft that would prevent this problem? I see no
reference in any of those articles to this specific problem. Furthermore, my
version of XP professional is always kept up to date with the Microsoft
Updates. Perhaps you could expand a little more?

 

[Peter Hibbs]

Tom is referring to this update :-

http://support.microsoft.com/kb/957924

As you can see, if you scroll to the bottom of the page, Microsoft has
disabled the MSCOMM32.OCX control with Windows Security Update 960715.
If you have Visual Basic 6 installed on your PC you can download the
updated versions of this (and a whole bunch of other controls) from
the same Web site which should fix the problem. If you haven't got
VB6, then complain to Microsoft.

Peter Hibbs.

 

[tkosel]

Peter and Tom,

Thanks for your update, Peter, Tom I am sorry I didn't dig deeper, the
information was there.

This is kind of bad news right? I think I am understanding that my
installation of security update 960715 is what caused this MScomm control to
cease to function? (Back around 2/11/2009 when the update was installed.)

If I remove 960715, will it start to work again? I am concerned about my
customer who uses the application that I wrote for them with the comm
control. If they install the update, the comm control will cease to function
right?

I do have VB6 installed, so if I install the referenced
VB60SP6-KB957924-v2-x86-ENU.msi, I understand that the control in Access
should work again too right?

So, if my customer installs 960715 and the mscomm control stops working, can
I distribute the control in VB60SP6-KB957924-v2-x86-ENU.msi to them legaly
and expect it to work again?

What other methods would be available in off the shelf Access to support
serial communications if they no longer support that control?

Again, thanks for your help, any additional tips would be appreciated.

 

[Peter Hibbs]

Comments in line.

Peter Hibbs.

Peter and Tom,

Thanks for your update, Peter, Tom I am sorry I didn't dig deeper, the
information was there.

This is kind of bad news right? I think I am understanding that my
installation of security update 960715 is what caused this MScomm control to
cease to function? (Back around 2/11/2009 when the update was installed.)

Certainly annoying and yes, that update did kill a lot of ActiveX
controls (MSFLXGRD.OCX in my case).

If I remove 960715, will it start to work again? I am concerned about my
customer who uses the application that I wrote for them with the comm
control. If they install the update, the comm control will cease to function
right?

It will work again BUT the next time your PC talks to the Microsoft
Servers the Security Update will get re-installed. I tried that one.

I do have VB6 installed, so if I install the referenced
VB60SP6-KB957924-v2-x86-ENU.msi, I understand that the control in Access
should work again too right?

Correct (well it did for the flexgrid control so I assume the Comm
control will do the same).

So, if my customer installs 960715 and the mscomm control stops working, can
I distribute the control in VB60SP6-KB957924-v2-x86-ENU.msi to them legaly
and expect it to work again?

Yes. As I understand it from the MS Web sites the VB6 update is to
allow developers to download the updated controls and then distribute
the specific controls with their applications to their clients.

What other methods would be available in off the shelf Access to support
serial communications if they no longer support that control?

Well they do still support the control, you just need to use the
latest version.

Sorry, don't know much about Comm controls. Perhaps Google might show
something.

 

[tkosel]

Peter,

Thanks for your inciteful responses. Installation went fine and the control
now works again. I will distribute the new MSCOMM32.OCX to my client. Final
question though. Why couldn't a a user who does not have VB6 installed
download and install this same package? Seems like it just installed the
updated OCX to the previous location, "C:\WINDOWS\system32\MSCOMM32.OCX


Thanks again.

 

[Peter Hibbs]

No good, I tried that idea on my laptop (which does not have VB6 on
it) and I just got a message to say it could not install the new
versions. I guess the installer program checks if VB6 is installed,
probably by looking in the Registry but I'm not sure.

Peter Hibbs.

 

[Tony Toews [MVP]]

I have a database that contains some Microsoft Communication Controls. I
used these ActiveX controls to interface to a serial device quite some time
ago and it has been working fine. The active X control is registered to
"C:\WINDOWS\system32\MSCOMM32.OCX"

See my blog posting on this topic:
An older version of MSCOMM32.OCX has had the "kill bit" flag set.
http://msmvps.com/blogs/access/arch...-has-had-the-quot-kill-bit-quot-flag-set.aspx

Tony

 

[Tony Toews [MVP]]

Also see Serial Port Communications page at my web site.
http://www.granite.ab.ca/access/serialport.htm for additional info if
required.

Tony