Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
access 2010: "object or class does not support the set of events"
110 views
Skip to first unread message
(PeteCresswell)
Feb 19, 2016, 2:00:15 PM2/19/16
to
This just started recently for one of my users.
Fired up the app on my developer box and got the same thing.
Googling, I see what way back in 2013 an MS security fix called MS12-060
hosed a lot of ActiveX controls. On the surface, this has a similar
look/feel to me.
So.... has anybody heard/seen recent events like this?
--
Pete Cresswell
Fired up the app on my developer box and got the same thing.
Googling, I see what way back in 2013 an MS security fix called MS12-060
hosed a lot of ActiveX controls. On the surface, this has a similar
look/feel to me.
So.... has anybody heard/seen recent events like this?
--
Pete Cresswell
Ron Paii
Feb 19, 2016, 2:42:43 PM2/19/16
to
"(PeteCresswell)" <x...@y.Invalid> wrote in message
news:hdpecbtcfglfucm1v...@4ax.com...
https://support.microsoft.com/en-us/kb/2748410 for a document that will fix
it. You will need to re-register the MSCOMCTL.OCX control on each computer
affected.
From an elevated command prompt on a 64-bit system
Regsvr32 /u "c:\Windows\SysWOW64\MSCOMCTL.OCX"
Regsvr32 "c:\Windows\SysWOW64\MSCOMCTL.OCX"
(PeteCresswell)
Feb 19, 2016, 4:31:31 PM2/19/16
to
Per Ron Paii:
But *if* that is actually the problem, it begs the question of "Why
Now?"...... Unless corporate IT is sooooo far behind in applying MS
security updates that they just put that one in a couple of days ago.
I guess I had better try their fix - although my recollection of that
particular debacle is that the MS-prescribed fix did not quite work and
I had to apply somebody else's variation on it.
--
Pete Cresswell
>That is an old problem 2012. See
>https://support.microsoft.com/en-us/kb/2748410 for a document that will fix
>it. You will need to re-register the MSCOMCTL.OCX control on each computer
>affected.
Yeah, I found that as soon as I started Googling.
>https://support.microsoft.com/en-us/kb/2748410 for a document that will fix
>it. You will need to re-register the MSCOMCTL.OCX control on each computer
>affected.
But *if* that is actually the problem, it begs the question of "Why
Now?"...... Unless corporate IT is sooooo far behind in applying MS
security updates that they just put that one in a couple of days ago.
I guess I had better try their fix - although my recollection of that
particular debacle is that the MS-prescribed fix did not quite work and
I had to apply somebody else's variation on it.
--
Pete Cresswell
pstan...@gmail.com
Feb 19, 2016, 7:00:48 PM2/19/16
to
The version I use is 6.1.98.46 Date modified 09/12/2015 (Suspect that is September) Product Version 6.01.9846.
Phil
(PeteCresswell)
Feb 19, 2016, 9:17:17 PM2/19/16
to
Per pstan...@gmail.com:
--
Pete Cresswell
>
>There are a lot of versions of MSCOMCTL.OCX, some of which work with Access 2010 and some that don't.
>The version I use is 6.1.98.46 Date modified 09/12/2015 (Suspect that is September) Product Version 6.01.9846.
Thanks!.... That gives me something to check against.
>There are a lot of versions of MSCOMCTL.OCX, some of which work with Access 2010 and some that don't.
>The version I use is 6.1.98.46 Date modified 09/12/2015 (Suspect that is September) Product Version 6.01.9846.
--
Pete Cresswell
0 new messages