|
-
Mar 28th, 2007, 06:22 AM
#13
Re: Excel dies only when userform disposed?
The index link is in my signature in red. 
Even if you set the object variable = Nothing that will not destroy an Office app reference. Then depending on how the code was written you may be creating additional references unknowingly.
Yes, that does make it hard to debug when its a good sized app. I would say to first start on all the Dim's and dimensioning of Excel object variables. They should be fully qualified and not just "Dim oRange As Range". That will create the implied extra reference. Whereas if you went "Dim oRange As Excel.Range" its explicit and no extra reference.
What does your "Imports" look like? Are you using the .Interop or the .Core?
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
|