|
-
Jun 4th, 2008, 12:51 AM
#5
Re: BackgroundWorker - Destroy Excel Instance
Sup Bruce! 
It not a recommended way to "clean" an Excel instance by calling the GC. Having the instance of Excel remain running after the app closes is usually from implied instanciation of Excel objects or not properly closing and destroying your Excel objects.
It looks like you are closing/destroying Excel ok but try creating an object var for each level of access you drill down the EOM.
Code:
Dim oWB As Excel.Workbook = oExcel.Workbooks.Open(CType(e.Argument, String))
'Could be re-written as ...
Dim oWBs As Excel.Workbooks = oExcel.Workbooks
Dim oWB As Excel.Workbook = oWBs.Open(CType(e.Argument, String))
Then close/destroy as you are logically are doing but loose the GC.
Last edited by RobDog888; Jun 4th, 2008 at 01:17 AM.
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum. 
Microsoft MVP 2006-2011
Office Development FAQ (C#, VB.NET, VB 6, VBA)
Senior Jedi Software Engineer MCP (VB 6 & .NET), BSEE, CET
If a post has helped you then Please Rate it! 
• Reps & Rating Posts • VS.NET on Vista • Multiple .NET Framework Versions • Office Primary Interop Assemblies • VB/Office Guru™ Word SpellChecker™.NET • VB/Office Guru™ Word SpellChecker™ VB6 • VB.NET Attributes Ex. • Outlook Global Address List • API Viewer utility • .NET API Viewer Utility •
System: Intel i7 6850K, Geforce GTX1060, Samsung M.2 1 TB & SATA 500 GB, 32 GBs DDR4 3300 Quad Channel RAM, 2 Viewsonic 24" LCDs, Windows 10, Office 2016, VS 2019, VB6 SP6 
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|