2013-03-07, 22:01 #1
- Join Date
- Oct 2002
- Blue Mountains, New South Wales, Australia
- Thanked 0 Times in 0 Posts
Workbook VBA project stays in memory after the workbook is closed
Using Windows 7 and Excel 2010
When I close an Excel workbook, the workbook and modules are still listed in the VBA project explorer.
If I open the same workbook twice, the modules are listed TWICE in the VBA project explorer.
I cannot see a command to remove it, so need to exit and restart Excel.
Is there a way to remove the project without restarting Excel????
Subscribe to our Windows Secrets Newsletter - It's Free!
Get our unique weekly Newsletter with tips and techniques, how to's and critical updates on Windows 7, Windows 8, Windows XP, Firefox, Internet Explorer, Google, etc. Join our 480,000 subscribers!
+ Get this BONUS — free!
Get the most of Excel! Learn about new features, basics of creating a new spreadsheet and using the infamous Ribbon in the first chapter of Excel 2013: The Missing Manual - Subscribe and download Chapter 1 for free!
2013-03-08, 00:28 #2
- Join Date
- Jan 2001
- Melbourne, Victoria, Australia
- Thanked 143 Times in 136 Posts
I'm also using Windows 7 and Excel 2010.
I don't see the same behaviour as what you describe so I'm guess there is an add-in that is causing your problem. What else is loaded? Can you disable them and test again?Andrew Lockton, Chrysalis Design, Melbourne Australia
2013-03-10, 00:21 #3
- Join Date
- Aug 2010
- Pa, USA
- Thanked 212 Times in 198 Posts
After doing some search regarding your symptoms, there are many who are experiencing the same problem with the work around of restarting excel to remove the duplicate VBA project. It seems that no one has specifically pinpointed a cause and/or a resolution, however, the majority of those with the problems have add-ons installed as Andrew implied. The most popular suggestion was to remove all the add-ons then reinstall one-by-one until the problem resurfaced thus identifying the culprit. However, there were those who had no add-ons installed who were experiencing the problem as well as those who had add-ons, removed them, and the problem never abated. This causative factor seems very vague with no definite solutions and Microsoft is not offering much help only occasionally referring to it as a bug.