I don't get the navigation bar, address bar, or any other controls on my web browser control. However, the pdf form itself inside of the web browser control is a separate matter. That is controlled by the properties of the pdf's controls, fields, and the pdf file itself. A pdf form needs to have its properties set to readonly, the toolbar turned off, the menu turned off (most don't know that just pressing F8 and F9 toggle these), and if the form itself is not set to readonly or a security level set then you can step through the controls and 'flatten' them which makes them so. There are 3rd party tools out there to do that as well - we use gnostice pdf tools (from www.gnostice.com). You may find one cheaper out there on the web though that does that for you.



>We don't want to show navigation bar, address bar, all other things associated with the Browser. We may also want to disable context menues.
>
>>Why doesn't the web browser control work for you? If all of the controls or fields on a pdf form are flattened, they are all readonly...
>>
>>>>When I put your code in the load of the form, it worked fine. I had to manually select the Adobe 7 Activex Browser control, but the form displays fine. We switched to the webbrowser control though inhouse due to the form stacking in Adobe.
>>>
>>>Hi Tracey,
>>>
>>>If you uncomment the OLE class in my code, you would get the error. I don't want the dialog to pick up class in run-time.
>>>
>>>Also by googling I found several free ActiveX viewers, but haven't evaluated them yet. We have a requirements here to be able to only view PDF, but disable almost all other functionality, e.g. no toolbars, etc. My colleague was able to partially achieve this goal by using JavaScripts and WebBrowser control, but we're not happy with this solution due to security risk..