I have written an application that uses an Excel template to print as follows, after populating the spreadsheet:

  'print the active sheet
  objWks.PrintOut Copies:=dblNumCopies, Collate:=True
  objWkb.Close SaveChanges:=False
  'close the objects
  Set objExcel = Nothing
  Set objWkb = Nothing
  Set objWks = Nothing


I have found however that the EXCEL object does not close when checking taskmanager. I assume that this is because the printer is busy with the sheet even after I have closed it. After the printing completed nothing closes the EXCEL object as my code has run already and the object stays open.

Is there any way that I can have my application wait on the printin to be completed before I close the object. I have tried looking at API calls to try and figure this out but the challange is to ask the printer for a message that my specific print job is completed. (This is because the printing is sent to a network printer where more than one person could be printing.

Please help.

Have you tried doing this first?

objExcel.Close


Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division

I have declared obj Excel as follows

   Set objExcel = New Excel.Application

It unfortunately does not have a .Close parameter. Thanks for your suggestion though!

Any other thoughts?

Bruce

See "50 Ways to Kill Excel"
http://www.devcity.net/Articles/239/1/article.aspx

There was a bug regarding using Word that was similar to this. There was also a very specific work-around, though I forget what that work-around was.

I have this niggling remnant of a memory that is was something like: after closing Word, using GetObject() to obtain a reference to that instance that ought not to be there, and again invoking the command to close the app.

I thought it was:

objExcel.Quit(false) (The false suppresses the save dialogue)

Cheers
Joe