Tracy,

I'm testing your code and the reader appears on every machine I have tested. I can kill the acrobat reader process using WMI code I found here, but without control of the reader process, the amount of time to allow printing to finish is an guessing game.

I guess it really doesn't matter if the reader appears on the taskbar. Subsequent calls to ShellExecute continue to use the same process. I could always kill it when my app shuts down. The problem I have is that the initial call to ShellExecute that creates the new instance of the Reader leaves focus on the reader on the taskbar. Do you know of any way to set focus back to my app?

Thanks