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/2597986Office 2007 w SP2 or SP3 -
http://support.microsoft.com/kb/2687441Office 2003 w SP3 or Office 2003 Web Components w SP3 -
http://support.microsoft.com/kb/2687323I 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.
Ben Sugden
"Remember to enjoy hunting - and that means relishing the search for the product that has never been advertised or placed handily at the front of the shop; Life begins on the uppermost shelf, avoid guide books and top 10's like the plague." - Ramsey Dukes
