Opening Word document into form using WebBrowser Object

[gstylianou]

Good Morning

I have specified the path of a Word file that opens into WebBrowser Object on the form. The problem is when i open the form I receive the attached message and the user must select "Open" to see the file.

Below is the code I have on "On Load Form Event" for the opening the file, and I hope someone can help me to modify the code in order to stop receive the relevant message

Thanks in advanced

 

[Mike Krailo]

Word files are viewed in Word. If you want to view them in a browser, convert to pdf.

 

[Isaac]

I agree with Mike. You are getting this because a Webbrowser control is essentially using internet explorer. Internet explorer is not normally what people use to open word documents. When you try to use I.E. to "open" a file that I.E. is not intended to or able to open, it will display that message in order to TRY to do the only thing it knows how to do with an unknown file--download it for you.

Maybe it can be used for that, with some amount of addins, changes, or funky settings, but why be trying to do that?
The number of things that modern browsers will try to "do" for you FAR exceeds the number of things it makes any sense for people to try to use them for.

I think there are Access form controls that can be used to view other Office apps (spreadsheet, word, etc). Maybe you can try those.
I've never used them so can't comment further.

 

[isladogs]

In December. MS will release a new web browser control based on Chromium Edge. Whether that will allow you to bypass the warning messages on form load I cannot say. However I'm 99.99% certain you cannot get rid of them with the current web browser object

 

[gstylianou]

Hello my friends,

Everyone agrees that Internet Explorer is not the best way to do this. However, I attach the database as I have downloaded it from the forum since some months now, and I'm trying to make some changes so that I can work through the access form because there is a special reason.

Attached you can find my DB and everything else needed to make the above possible, but I want your help to avoid the relevant message

 

[isladogs]

IIRC that example was done by @arnelgp. I have my own version which is very similar.
I get the same messages and, as already stated, don't believe you can prevent them ...at least without a lot of work for little gain

 

[gstylianou]

IIRC that example was done by @arnelgp. I have my own version which is very similar.
I get the same messages and, as already stated, don't believe you can prevent them ...at least without a lot of work for little gain

Morning,

Yes, but can we try to do it?

 

[isladogs]

Sorry but having tried it some time ago, I really don't have the time to look into it further.
Good luck with any attempts you make and, if you succeed, do let us know how you did so.

Perhaps @arnelgp may see this and be willing to look into it further?

 

[gstylianou]

Sorry but having tried it some time ago, I really don't have the time to look into it further.
Good luck with any attempts you make and, if you succeed, do let us know how you did so.

Perhaps @arnelgp may see this and be willing to look into it further?

No problem, thanks again

 

[jaikaoliver]

In December. MS will release a new web browser control based on Chromium Edge. Whether that will allow you to bypass the warning messages on form load I cannot say. However I'm 99.99% certain you cannot get rid of them with the current web browser object

Has this been effected, I long to update my access apps with the new browser

 

[isladogs]

Not yet. The Access roadmap now shows this as being one of five items due for release Sept 2021 (this month). See Microsoft 365 Roadmap | Microsoft 365. However it looks like none of those will be ready on time. The MS priority is currently the Dataverse connector even though most developers would probably rate other items higherpriority

However, it is possible to get rid of the warning messages described in this thread using a registry fix

 

[jaikaoliver]

Not yet. The Access roadmap now shows this as being one of five items due for release Sept 2021 (this month). See Microsoft 365 Roadmap | Microsoft 365. However it looks like none of those will be ready on time. The MS priority is currently the Dataverse connector even though most developers would probably rate other items higherpriority

However, it is possible to get rid of the warning messages described in this thread using a registry fix

Noted.......,this part of registry please, is it like the internet explorer set for IE 11?

 

[isladogs]

No. Its more than that. I can't remember the details offhand but you should be able to find it somewhere ln this forum