PDFdev is a service provided by PDFzone.com | http://www.pdfzone.com _____________________________________________________________
"DANGER WILL ROBINSON! DANGER!" As has been mentioned on numerous occasions on this list, the PDF.OCX is not ment for our use. Adobe created it specifically for internet browser support, and does not support 3rd party development. No docs, no behaviors that might change radically from one release to another... digital mine field. So any development you do with it is just begging to be broken in the next release, whenever that might be. The next point-release of Acrobat could easily break your software, leaving you with some Unhappy end users (clients, customers, whatever you call them). Okay, you've been warned. There's at least one win32 system call you can make to force a process to terminate. How to call this from a VB app, and what side-effects it might have on the OCX I'll leave as the dreaded "excercise for the reader". But I really recommend looking elsewhere for your PDF display tech. If you review the list's archives, you'll find a number of suggestions. http://www.pdfzone.com/discussions/archives/1996_200304/pdfdev/search/index. asp Searching for "PDF.OCX" turned up 102 hits. Enjoy. --Mark Storer Software Engineer Cardiff Software #include <disclaimer> typdef std::disclaimer<Cardiff> Discard; > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 19, 2003 9:57 AM > To: [EMAIL PROTECTED] > Subject: [PDFdev] Acrord32.exe remains in NT process list for several > seconds > > > > PDFdev is a service provided by PDFzone.com | http://www.pdfzone.com > _____________________________________________________________ > > We have a VB app that runs on a Citrix server and uses the PDF.OCX to > display the PDF within our application. We add the control > to the form at > runtime. When our user clicks the application button that > displays the PDF > in our form, then exits the reader form, then goes back in, the pdf > re-displays as blank pages. If the user exits the reader > form, then waits > long enough for the acrord32.exe process to kill itself from > the NT process > list (about 15 seconds) then goes back in, the PDF > re-displays correctly. > > Is there a way to have acrord32.exe kill itself immediately after the > calling form is unloaded? Or is there a setting that will allow the > subsequent displays to behave properly even if the user > re-displays the PDF > before acrord32.exe unloads? Any input appreciated. > > Thanks, > Chris > > To change your subscription: > http://www.pdfzone.com/discussions/lists-pdfdev.html > To change your subscription: http://www.pdfzone.com/discussions/lists-pdfdev.html
