Mscomctl.ocx in memory?
Posted on 2012-08-24
I have an Access application that utilizes the mscomctl.ocx common library. With last week's Microsoft security update, they removed some 'vulnerable' controls from the library (one of which we were using). Therefore, we had to release a new version of our program with a new reference within our Access project to the 'new' mscomctl.ocx file and package it in our installer file.
It works like a charm in almost every instance, except one customer I am having problems with. For some reason half of their PC's are still throwing an error when they access the form that utilizes this control. I've tried manually re-registering, unregistering and re-registering the control to no avail. One thing I did notice is that another program that is loaded on these PC's utilizes it's own copy of mscomctl.ocx in a completely different directory.
So, my question is - I'm wondering if ocx files get loaded into memory somewhere and that perhaps what is happening is that my program is not even trying to use the 'new' ocx file, but rather reverting to an old version that is sitting in memory somewhere?