Member Avatar for ben.sugden

I am responsible for developing and maintaining a widescale CRM platform written with Visual FoxPro 9.0 (sp2 SEDNA).

Alongside a SQL 2008 back end, I make extensive use of the Microsoft Common Control libraries for the purposes of providing TreeViews, ListViews and the like (the kindof theing that VFP does handle well on its own).

I've used the controls in this manner for over a decade but this week have encountered a problem with my listviews. They simply refuse to allow me to alter columns.

Normally, you can right click the listview in the VFP development environment and select "Listview Properties" - go to the Column Headers and add, Remove, Alter columns to your heart's content.

Today, all the drop down lists in the ListView properties GUI are missing and I receive "Invalid Property Value" errors when trying to apply changes.

Now I haven't had cause to make changes in the code for a good month or so but have been developing the system in this way, using Windows 7 for almost a year without issue.

Does anyone know of anything happening to the Microsoft Common Controls libraries?

  • 1 Contributor
  • 1 Reply
  • 222 Views
  • 4 Days Discussion Span
  • Latest Post Latest Post by ben.sugden
Member Avatar for ben.sugden

It always seems bad form to reply to my own posts but I have found a cause and solution to my problem.

It seems there is an issue caused by a recent security update (MS12-060).

Fixes have been released by Microsoft, depending on your MS Office version:

Office 2010 w SP1 - http://support.microsoft.com/kb/2597986
Office 2007 w SP2 or SP3 - http://support.microsoft.com/kb/2687441
Office 2003 w SP3 or Office 2003 Web Components w SP3 - http://support.microsoft.com/kb/2687323

I didn't bother with these though as the general community consensus was to fix this manually by:

1) Unregister your mscomctl.ocx.
2) Rename your current version to something temporary.
3) Copy an older version to the same folder. (System32 or SysWOW64)
4) Register it.
5) Unregister it.
6) Rename the old copy or delete it.
7) Rename the original to mscomctl.ocx.
8) Register it one final time.

As convoluted as that seems, it worked and can be batched for me to run on my effected clients.

commented: Thanks for sharing. +13
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.