excel process not being terminated

[allenjasonbrown@gmail.com]

Can anyone look at the code below and give me some suggestions on why it would leave an excel.exe process running?

   Dim OutPutFileName As String
   
   strPath = "C:\temp\test.xlsb"
   Set ApXL = CreateObject("Excel.Application")
   Set xlWBk = ApXL.Workbooks.Open(strPath)
   ApXL.Visible = False
 iRowCountA = Range(xlWBk.Sheets("sheet1").Range("A2"), xlWBk.Sheets("sheet1").Range("A2").End(xlDown)).Rows.Count
 
   ApXL.Visible = True
   OutPutFileName = "C:\temp\test- " & Format(Now, "yyyymmdd hhmmss") & ".xlsb"
    xlWBk.SaveAs FileName:=OutPutFileName
    Set xlWBk = Nothing
    Set ApXL = Nothing

I have removed some other code but I know the line that starts with "iRowCountA......" is the culprit. If I comment it out that line there is no issues.

Thanks in advance.

[June7]

The code opens Excel and a workbook and then makes it visible and doesn't close Excel. Seems to me there should be a process running. Do you mean even after manually closing Excel a process is still running? I have encountered that as well, very aggravating. Not always sure what causes the process to persist.

Why do you need the row count?

[allenjasonbrown@gmail.com]

Yes sorry. After manually closing the excel (which I want open when the application finishes) I still get an excel process running. It then causes an error if I try and run the Access application again.

I use the row count to delete that number of rows from a different sheet.

[SteveH2508]

Try iRowCountA = ApXL.Range(xlWBk.Sheets("sheet1").Range("A2"), xlWBk.Sheets("sheet1").Range("A2").End(xlDown)).Ro ws.Count

This problem is usually caused by unqualified references to Excel so it creates another instance of Excel which is left running.
That is the only unqualified reference I can see (untested air-code)

[Dal Jeanis]

You definitely should have ApXL.Quit before SET ApXL = Nothing.

[June7]

Dal, I don't think that is actually required. If user wants to leave workbook open and continue working with it directly, that should be possible. The code can still release the variables. I have run code that opens Excel and workbook, edits the workbook and leaves the workbook open and I don't even bother releasing the variables and the process will terminate when I manually close Excel. Then there are times I have seen the process persist and figuring out why nearly drives me nuts, if I even ever figure out the why.

[Dal Jeanis]

June - wouldn't be absolutely required, but he's complaining about the process being left running... If that process has the potential to be run multiple times, and isn't going to quit the application, then it should be detecting whether the application is already running before creating a new one.

[June7]

Not sure even .Quit will assure the process is terminted. Seems I've run into that as well.

[Dal Jeanis]

The other possiblity is that it's quietly failing somewhere else, and not telling him it didn't get to the end of the code. The debug for that is changing the "on error" lines so that any errors will kick up a fuss.