[AccessD] Fixing the Microsoft Windows Common Control Library (MSCOMCTL.OCX) Security Update

Hi Dan

No, the cited reason was the only one listed. It seems valid, but it is an
awkward method to get rid of that entry.

/gustav


-----Oprindelig meddelelse-----
Fra: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] På vegne af Dan Waters
Sendt: 6. marts 2013 14:26
Til: 'Access Developers discussion and problem solving'
Emne: Re: [AccessD] Fixing the Microsoft Windows Common Control Library
(MSCOMCTL.OCX) Security Update

Hi Gustav,

As one who tried several ways to fix this - the FMS approach was the only
one I could count on.  I think the FMS site had a description of why it did
work.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Wednesday, March 06, 2013 3:23 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Fixing the Microsoft Windows Common Control Library
(MSCOMCTL.OCX) Security Update

Hi John

Thanks, but how convoluted can you do things:

<quote>
By installing and uninstalling the legacy control, it cleans up the 2.0
registry so the new version is installed properly. The offending registry
that needs to be deleted is:

HKEY_CLASSES_ROOT\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0
</quote>

So why not just delete this entry and reinstall the new version?

/gustav

-----Oprindelig meddelelse-----
Fra: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] På vegne af John Bartow
Sendt: 5. marts 2013 21:11
Til: DBA-Access
Emne: [AccessD] Fixing the Microsoft Windows Common Control Library
(MSCOMCTL.OCX) Security Update

I thought this was a concise set of instructions for those suffering this
problem:
http://www.fmsinc.com/MicrosoftAccess/Controls/mscomctl/

hth
John B