Very similar to this thread but re-registering the ocx files was a temporary fix.
The problem was first reported to me on the 13th. IT rolled out some updates over that weekend as shown in the attachment. Has anyone else experienced any problems and found a permenant (at least until the next MS updates) solution?
Following up on this i applied the suggested fix from
http://support.microsoft.com/kb/2687441
One machine i did manually the other i used the batch file. They have both stuck for three days so im inclined to distribute it as a fix (at least until the next windows updates).
FYI. Confirmed as NOT a bulletproof solution. Still have one machine that does not work.
More and more machines keep falling back to the same error so the linked solution is definitaley not 100% solid.
Can ayone suggest anything else?
I have attached a pic of the vba references. Its 99% likely all these machines use the standard coporate W7 x64 image with the standard MS OFfice 32bit 2010 professional plus install.