🚀 go-pugleaf

Dave,
my application allows the user to open files (".doc", ".txt", ".pdf", etc.) by tapping on the associated item in a ListView control.
Shelling to file explorer allows file to be opened relying on the registry content to run the proper "viewer".

It also has an interesting fallback: if you open a ".doc" or a ".txt" file invoking Shell ("\Windows\pword.exe", FILENAME), when the user taps on the "ok" button, Pocket Word closes the document and shows the full doc list (Pocket Word remains the "foreground" application)
Calling Shell ("\Windows\fexplore.exd", FILENAME) makes Pocket Word MINIMIZED WHEN THE USER TAPS ON THE "ok" BUTTON. The "foreground" application is now "File explorer".

Calling SetWindowPos just after the Shell function invocation with the "File explorer" window handle (retrieved by enumerating windows) and my application window handle as parameters modifies the window z-order and makes my application become the "foreground" application when Pocket Word gets minimized.

Despite of my efforts, I was not able to open more than ONE pdf file running acrord32.exe (that's the reason why I asked if you had find a way to terminate Acrobat process). I restored the opendoc registry key allowing PDF files to be opened by "ClearVue PDF Reader".

Everything is working fine.

Once again thanks for your help.