RE: Get url for pdf file from AxSHDocVw.AxWebBrowser

I not sure, but maybe when the webdisplay.document.all(0).outerhtml doesn't
work, it is the pdf file. So, how to I copy the object (which I think is the
pdf file) to a local folder?

"LN Mike" wrote:

Some of the "web pages" actually just let the acrobat reader take over the
entire browser control. I put a break point on my brower control
"DocumentComplete" event, so I'm able to see each and every page that comes
through. However with the web sites that I can't get a src tag, I can't open
the document at all, it seems DocumentComplete sends me a pdf file not a html
file, so I can't see outerhtml.

WebDisplay.Document.All(0).outerhtml gives me the following error message

Run-time exception thrown : System.MissingMemberException - Public member
'All' on type 'IAcroAXDocShim' not found.

But with the web sites that do work, I'm able to see the html code that has
the src tag.

""Jie Wang [MSFT]"" wrote:

Hello Mike,

When you say "some web sites don't provide the web page with a src tag", do
you mean those "web pages" actually just let the Acrobat reader take over
the entire browser control (the PDF document was fully filled into the
control)? Or those web pages uses other means to embed a PDF file as a
portion of the entire HTML page?

Could you give me a specific sample of the problem you met so I can better
understand the situation and see if we can come out a solution to it?


Jie Wang (jiewan@xxxxxxxxxxxxxxxxxxxx, remove 'online.')

Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:

Get notification to my posts through email? Please refer to

Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 2 business days is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions. Issues of this
nature are best handled working with a dedicated Microsoft Support Engineer
by contacting Microsoft Customer Support Services (CSS) at
This posting is provided "AS IS" with no warranties, and confers no rights.