[AccessD] Excel Not Closing

[Stuart McLachlan]

Searching through my archives, it's a long time sionce this one came up, but it used to be 
fairly regular (the last time was in Jun 2014):

Here's what I said in 2009:

On 14 Nov 2009 at 8:29, Stuart McLachlan wrote:

> Third time I've answered this on the list this year. 
> 
> See:
> TrasnferSpreadsheet failing  on 18 March 2009
> and 
> Access to Excel Automation works first time on 13 July 2009:
> in the archives.
> 
> The old "unqualified reference" strikes again :-)
> See http://support.microsoft.com/kb/319832
> 
> <quote> When you write code to use an Excel object, method, or
> property, you should always precede the call with the appropriate
> object variable. If you do not, Visual Basic establishes its own
> reference to Excel. </quote>
> 
> 


On 10 Apr 2023 at 10:55, Rocky Smolin wrote:

> Dear List:
> 
> I have an app which exports data to an Excel spreadsheet.  It is not
> amenable to using TransferSpreadsheet because of formatting problems,
> etc. So I use the brute force method and it works well.
> 
> Problem is that at the end of the process the user wants the app to
> open the spreadsheet.
> 
> So I use Application.FollowHyperlink strFileName. Problem is that the
> spreadsheet opens blank.
> 
> When I go to the folder and open the spreadsheet it's there, all
> perfect. So I put a breakpoint in at the statement
> Application.FollowHyperlink strFileName and looked at the Task Manager
> and sure enough there was an instance of Microsoft Excel still there
> in the list of background processes.
> 
> If I end that Excel process and then let the app execute the Follow
> Hyperlink it opens just fine. So it's that leftover instance of Excel
> that's hosing up the works.
> 
>  I set the objects like so:
> 
> Set objXLApp = New Excel.Application
> Set objXLBook = objXLApp.Workbooks.Add
> Set objXLWS = objXLBook.Sheets(1)
> 
> and at the end close up like so:
> 
> objXLBook.SaveAs strFileName
> objXLBook.Close True
> 
> Set objXLWS = Nothing
> Set objXLBook = Nothing
> 
> objXLApp.Quit
> Set objXLApp = Nothing
> 
> How do I get rid of that instance of Excel in the background
> processes?
> 
> 
> MTIA
> 
> Rocky
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>