KB2687441 causing problems with common controls in Access-based System
After installing Security Update for Microsoft Office 2007 (KB2687441) our Access 2007 based project management system has stopped working. Unfortunately, this particular update is not removable.
The first problem we discovered that when certain forms were opened, they would close straight away and fire the error "The OpenForm action was cancelled".
I tried unregistering and then re-registering MSCOMCTL.OCX. This did not help.
I then tried unregistering it, copying an older version of the file from a machine that hadn't been updated yet, and re-registering that version.
This solved the above error.
However, we have found that there are still some issues. Any form that contains a ListView control or a TabStrip control will fail on startup with errors such as "Object doesn't support this property or method" whenever these controls are referenced. (In particular, we are calling the ItemsItems.Clear method on the ListView, and trying to reference the caption property of a tab in the tab strip.)
None of these problems exist on machines that haven't installed KB2687441.
It was my understanding that both the tabstrip and listview were stored in MSCOMCTL.OCX, but I'm guessing there must be some other files that I also have to roll back to overcome these problems.
Any thoughts?
The first problem we discovered that when certain forms were opened, they would close straight away and fire the error "The OpenForm action was cancelled".
I tried unregistering and then re-registering MSCOMCTL.OCX. This did not help.
I then tried unregistering it, copying an older version of the file from a machine that hadn't been updated yet, and re-registering that version.
This solved the above error.
However, we have found that there are still some issues. Any form that contains a ListView control or a TabStrip control will fail on startup with errors such as "Object doesn't support this property or method" whenever these controls are referenced. (In particular, we are calling the ItemsItems.Clear method on the ListView, and trying to reference the caption property of a tab in the tab strip.)
None of these problems exist on machines that haven't installed KB2687441.
It was my understanding that both the tabstrip and listview were stored in MSCOMCTL.OCX, but I'm guessing there must be some other files that I also have to roll back to overcome these problems.
Any thoughts?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Do a search for .exd files that share the same name. They are in a folder under the users folder, I think under AppData... Anyway search for the .exd extension and be sure the search hidden folders.
Once you find the files, delete them. They will be recreated by the vb runtim libraries.
For more info, do a bing/google search for "delete exd files", and you will get more information on this.
Once you find the files, delete them. They will be recreated by the vb runtim libraries.
For more info, do a bing/google search for "delete exd files", and you will get more information on this.
ASKER
Thankyou for all the good suggestions.
Our ICT manager was not willing to go along with using System Restore to roll back the update so we had to find a way to make the system work with the update in place.
I agree that using all these controls in Access is not ideal. To give some context, this system has 94000 lines of code in about 800 forms, reports and modules, so even if our users were willing to live without the features of listviews over list boxes, and we found a way to get around the Tab control, we'd still be looking at a mammoth effort to strip them all out. I understand that a system this size is not best suited to Access, but it's the system we have in place and need to support.
In the end, we overcame this issue by:
1) un-registering the new control
2) reistering the old control
3) un-registering the old control
4) re-resitering the new control.
As several of you have pointed out, this is a 'band-aid'. Hopefully in time we can gradually replace this with something more stable.
thank you all for you input.
Our ICT manager was not willing to go along with using System Restore to roll back the update so we had to find a way to make the system work with the update in place.
I agree that using all these controls in Access is not ideal. To give some context, this system has 94000 lines of code in about 800 forms, reports and modules, so even if our users were willing to live without the features of listviews over list boxes, and we found a way to get around the Tab control, we'd still be looking at a mammoth effort to strip them all out. I understand that a system this size is not best suited to Access, but it's the system we have in place and need to support.
In the end, we overcame this issue by:
1) un-registering the new control
2) reistering the old control
3) un-registering the old control
4) re-resitering the new control.
As several of you have pointed out, this is a 'band-aid'. Hopefully in time we can gradually replace this with something more stable.
thank you all for you input.
<To give some context, this system has 94000 lines of code in about 800 forms, reports and modules, so even if our users were willing to live without the features of listviews over list boxes, and we found a way to get around the Tab control, we'd still be looking at a mammoth effort to strip them all out. I understand that a system this size is not best suited to Access, but it's the system we have in place and need to support.>
Thanks...
Most Experts here try just to notify folks of the downsides of these controls.
We won't beat you over the head with it though...
;-)
...because most all of us to are faced with projects where we have to:
"Build with the Bricks we are given"
We are all glad that our posts helped you work toward a resolution.
;-)
Jeff
Thanks...
Most Experts here try just to notify folks of the downsides of these controls.
We won't beat you over the head with it though...
;-)
...because most all of us to are faced with projects where we have to:
"Build with the Bricks we are given"
We are all glad that our posts helped you work toward a resolution.
;-)
Jeff
deleting the registry entry
[HKEY_CLASSES_ROOT\TypeLib
solved our problems with mscomctl.ocx