<div>
Question<br />
When you close the workbook thru VBA if you open task manager is there an Excel instance running or not ?<br />
<br />
gowflow
</div>


<div>
Without seeing the code you are trying to run it is hard to say. If you are spinning off new instances of Excel, then what gowflow is suggesting is that you may not be properly quitting and destroying the new Excel processes.
</div>


<div>
If you believe your a pro then fine. Reason why you came here is for help. As Patrick nicely outlined, and what I thought of also is that your workbooks are not closing properly !!! I quote again your first para<br />
<br />

<blockquote>
<br />
I have an Excel VBA app that creates a number of other Excel workbooks. &nbsp;It also opens/closes a number of workbooks in order to accomplish its tasks. &nbsp;The app closes each workbook it creates and/or opens as soon as it is through working with it.<br />

</blockquote>
<br />
I once stayed 1 Full week looking at my code and asking myself (although I properly 'closed' Excel and quited but still it was open ... all this to say, you maybe convinced that you are closing properly your workbboks but fact of the matter is : Your using extensive memory and this is annoying to you.<br />
<br />
So to make a long story short unless you post your Entire code that is causing this issue we are sorry: But can't help you further. I would very much understand you not wanting to disclose a code which we all feel proud of when we spend lots of time developing but if you want a solution then got to give in somewhere.<br />
<br />
PS: Maybe Excel is closing BUT you are maybe creating Arrays over Arrays over Variables that are not being cleared and maybe these are Memory hungry all depends if they are declared at module or local level and all depends on the setup of workbooks. So many issues can come into account.<br />
<br />
Gowflow
</div>


<div>
I am looking at the Task Manager. &nbsp;So I can see what processes are running. &nbsp;I can see that the original code is not spawning any new Excel apps. &nbsp;I can see that my code is properly killing all Excel apps that it creates.<br />
<br />
If you want to see this yourself, all you need to do is bring up Excel and then open and close a bunch of large Excel files while viewing the Task Manager. &nbsp;You will see that your Working memory will creep up even though you are closing the workbooks.<br />
<br />
The code I am working with queries data from SQL Server, generates tables of data, performs a few calculations, generates plots, and then closes the workbooks. &nbsp;Yes the code uses arrays, but the arrays are part of the code which is part of the workbook. &nbsp;If Excel is behaving properly then when the workbook is closed, all of the associated objects should be freed from memory. &nbsp;Excel may be trying to be &quot;smarter&quot; than me by keeping the workbook in memory. &nbsp;It may believe that I will open it again sometime in the near future. &nbsp;However, in this case the behavior is problematic.<br />
<br />
Here are links to some of the sites I googled for an answer. &nbsp;You will see this is a prevalent problem that others have experienced with different code. &nbsp;This seems to be a problem with various versions of Excel on various OSes:<br />
<br />
<a href="http://stackoverflow.com/questions/27111901/excel-doesnt-release-memory-on-workbook-close" rel="ugc">http://stackoverflow.com/questions/27111901/excel-doesnt-release-memory-on-workbook-close</a><br />
<br />
<a href="https://social.msdn.microsoft.com/Forums/vstudio/en-US/04cbb306-278a-462a-b0a6-f666a19aad8c/why-does-excel-2016-not-release-memory-after-the-wokbook-is-closed?forum=exceldev" rel="ugc nofollow">https://social.msdn.microsoft.com/Forums/vstudio/en-US/04cbb306-278a-462a-b0a6-f666a19aad8c/why-does-excel-2016-not-release-memory-after-the-wokbook-is-closed?forum=exceldev</a><br />
<br />
<a href="https://excel.uservoice.com/forums/304921-excel-for-windows-desktop-application/suggestions/9555807-release-memory-after-large-workbook-is-closed" rel="ugc">https://excel.uservoice.com/forums/304921-excel-for-windows-desktop-application/suggestions/9555807-release-memory-after-large-workbook-is-closed</a><br />
<br />
The only proposed solution was to alter the registry, which as I said is not an option for applications that are run on multiple computers in a company that doesn't allow regular users to have admin privileges.
</div>


<div>
So seems your more knowledgeable in this area as have done your due diligence and have all supporting proves and docs. I wonder why at the first place you asked the question !!!<br />
<br />
Maybe to teach us ?<br />
<br />
I strongly suggest you find the proper channels to address requests to Microsoft to handle this issue maybe then your time would pay off.<br />
gowflow
</div>


<div>
well said gowflow.<br />
<br />
you should address this issue via uservoice feedback to Microsoft via <a href="https://excel.uservoice.com/" rel="ugc">https://excel.uservoice.com/</a>&nbsp; &nbsp;Excel user voice is the best place for customers to provide feedback and &nbsp;MSFT folks are looking into that regularly.
</div>


<div>
BRAVO !!! Professor didn't know that existed well done !<br />
gowflow
</div>


<div>
A number of programmers have brought this to Microsoft's attention to no effect. &nbsp;Even if MS fixes this, it will be in some future version of Excel that my company will not support until some years in the future. &nbsp;We currently only support Excel 2013. &nbsp;We're behind because every new upgrade has to be thoroughly tested to see there are no security holes and that it works with all our current applications.<br />
<br />
I was hoping there might be some cool trick that would get Excel to flush the memory cache, but I guess not.<br />
<br />
BTW, the code that I inherited is HORRIBLE. &nbsp;It looks like what happens when someone just records a macro and surrounds the code with 'sub' and 'end sub'. &nbsp;It's sometimes difficult to figure out what workbook or worksheet or chart that the code is acting upon. &nbsp;I'm sure that some of the memory leakage is due to this sloppiness. &nbsp;However, when I rewrote some of the code to explicitly associate all of the objects it didn't really help much.<br />
<br />
Oh well. &nbsp;Thanks for listening. &nbsp;I wasn't trying to show off what I found out. &nbsp;I was just hoping for some clever trick to clear out the memory.
</div>


<div>
Sorry if u felt offended, but sometimes comments do get wrongly interpreted especially in here. Good luck with your endeavors anyway.<br />
gowflow
</div>


<div>
No better alternative was proposed.
</div>


<div>
<div class="content wysiwyg-content">
I have an Excel VBA app that creates a number of other Excel workbooks. &nbsp;It also opens/closes a number of workbooks in order to accomplish its tasks. &nbsp;The app closes each workbook it creates and/or opens as soon as it is through working with it. &nbsp;However, as the app executes the memory used by the Excel app continues to climb. &nbsp;For some users it runs out of memory/resources before completing the task.<br />
<br />
I have done some googling. &nbsp;One recommendation is to modify the registry settings to disable logging. &nbsp;However, this program has to run on multiple computers and changing this particular registry setting requires admin privileges which most users do not have.<br />
<br />
Is there a way to get Excel to release the memory of a workbook when it's closed?<br />
<br />
There are numerous workarounds to this problem (e.g. rewrite in another language, rewrite as a VB rather than VBA app, write a shell program that launches a new Excel app for each workbook processed, etc.) &nbsp;However, this problem is affecting multiple VBA apps which were just recently dumped on me. &nbsp;Having to rewrite all those scripts along with my regular duties would be daunting.<br />
<br />
This is running on Windows 7.
</div>
</div>


I have an Excel VBA app that creates a number of other Excel workbooks.  It also opens/closes a number of workbooks in order to accomplish its tasks.  The app closes each workbook it creates and/or opens as soon as it is through working with it.  However, as the app executes the memory used by the Excel app continues to climb.  For some users it runs out of memory/resources before completing the task.

I have done some googling.  One recommendation is to modify the registry settings to disable logging.  However, this program has to run on multiple computers and changing this particular registry setting requires admin privileges which most users do not have.

Is there a way to get Excel to release the memory of a workbook when it's closed?

There are numerous workarounds to this problem (e.g. rewrite in another language, rewrite as a VB rather than VBA app, write a shell program that launches a new Excel app for each workbook processed, etc.)  However, this problem is affecting multiple VBA apps which were just recently dumped on me.  Having to rewrite all those scripts along with my regular duties would be daunting.

This is running on Windows 7.

Excel 2010:  Not releasing memory when workbooks closed

Visual Basic for Applications (VBA) enables building user-defined functions (UDFs), automating processes and accessing Windows API and other low-level functionality through dynamic-link libraries (DLLs). VBA is closely related to Visual Basic and uses the Visual Basic Runtime Library, but it can normally only run code within a host application rather than as a standalone program. It can, however, be used to control one application from another via OLE Automation. VBA is built into most Microsoft Office applications.

Microsoft Excel topics include formulas, formatting, VBA macros and user-defined functions, and everything else related to the spreadsheet user interface, including error messages.

Microsoft Excel

Microsoft Office is an integrated suite of applications that includes Outlook, Word, Excel, Access, PowerPoint, Visio and InfoPath, along with a number of tools to assist in making the individual components work together. Coding within and between the projects is done in Visual Basic for Applications, known as VBA.