Jos,

I use Adobe 5 and this happens frequently to me as well.
I have created com-objects that create pdf-files that are shown in the browser. Sometimes the reports are not shown. It took a while to determine but it became clear that Adobe is doing things on its own. Once I terminate the Adobe process things become normal.

I have not found a 'better' solution yet. If you find please let me know.

Regards,

Ron

>Hi Dave. This is exactly my gripe with Adobe too. Acrobat 4 does this. Not sure if it has been changed in subsequent versions. What a memory hog. Plus, one about 1 in 10 occurances it actually crashes IE !
>
>>Tracy,
>>
>>This doesn't answer your question directly, but FWIW, If I view a pdf from the web inside IE, and close browser instance. Adobe blindly sits there in memory chewing up about 37mb, just waiting around for another chance to view a pdf... it's about the most piggish program that I've ever seen in this respect. I assume that is because it takes so bloody long for the stupid thing to load all of it's addins in the first place. Anyway I've gotten in the habit of taskmanagering the stupid thing to get rid of it.
>>
>>>When I start either Adobe Acrobat or Adobe Acrobat Reader using createprocess as in the code below, it starts fine. However, when I close either app (acrobat or reader), it appears that the process never ends under windows task manager so the waitforsingleobject never stops waiting. I have to go to windows task manager and kill the process for waitforsingleobject to stop waiting.
>>
>>>1. Acrobat Reader be installed
>>>2. Registry.vcx and the path to it stored in xregclass var.
>>>3. A .PDF form with the path included stored in xacordform var.
>>>
>>>I'm wondering if anyone else can duplicate it? It does it everytime to me...