I got code working that launches the pdf in Adobe Reader (createprocess with the /p) and displays the print dialog box but when the user clicks on Print or Cancel Adobe Reader is still open of course. I suspend processing in VFP (getexitcodeprocess) while Adobe Reader is open which will not work in this case the way I want it to. The user is forced to manually close Adobe Reader after printing or clicking on cancel or else the vfp app remains suspended because it is looking for the Adobe Reader process to quit. Ideally I would:

1. Launch the pdf in Adobe Reader nonvisual and automatically launch the print dialog window. ->DONE
2. Suspend processing in VFP until the Adobe process exists. ->DONE
3. When the user clicks on Print or Cancel, EXIT ADobe Reader automatically. ->PROBLEM
4. Return processing to VFP when the Adobe Reader process exits. ->DONE

As you can see, item #3 is the problem unless I let the users be responsible for not only clicking on Print or Cancel in the Adobe Reader print dialog window, but also manually closing the reader afterwards so processing can return to VFP.

Tracy