Access Modern Web Browser Control – End Of The Road

Figure holding a stop sign

I just wanted to state that I most probably won’t be pursuing any more development using the new ‘Modern’ Web Browser control for a little while.

I’ve:

  • shown you all the basics
  • shown how you can even perform more advanced automation
  • provided a couple demos
    • merge/split PDFs
    • webcam automation and I do hope that helps a few of you out there

That said, sadly, I had several other demos planned and have hit walls on all of them as the new control does not support some JavaScript code (createObjectURL for instance – which works fine in Edge itself OR something as simple as document.location.href = …) or because of the loss of the Object.Document I can no longer automate things like I could do so easily with the old browser control. So until such time that Microsoft provides us with a fix, I simply cannot move forward with any of them. So more and more, I’m learning the the Access Modern Web Browser control does not equal Edge. It may approach it, but it certainly is not the same thing and there are stark differences and limitations. (for anyone wondering, this and much more has all been provided to Microsoft, so they are aware of it all)

Please, don’t get me wrong, the new control has some very nice benefits and solves some serious issues we had with the old control, but sadly it also appears to have some serious limitations that truly impact advance automation use cases and even plain and simple everyday web surfing (I’m referring to Trusted Domains, not allowing mixed content sources, not fully supporting JS, …)!

For me, because of the limitation imposed by Microsoft, the Modern Web Browser control is in fact a Modern Web Page Viewer control and NOT a Web Browser control unlike its predecessor which was a proper Web Browser control.

So enjoy the new control to access the web if it meets your needs, but at this point in time I’m taking option 2 from my original post on the matter and going to wait and see if Microsoft fixes things (I doubt they will though, prove me wrong Microsoft!) before investing more time and energies into working with the control any further. It’s still been a fun ride figuring all of this out.

3 responses on “Access Modern Web Browser Control – End Of The Road

    1. Daniel Pineault Post author

      Interesting. In my case I was simply evaluating the newly introduced feature from Microsoft. I’m not requiring any 3rd party tools. Furthermore, getting into distributing ActiveX controls as part of an Access database, or any other project for that matter, is not something I recommend. That said, for some, this might be an interesting alternative to explore. Thank you for sharing.

  1. Walter van der Geest

    I gave up after 3 weeks. The path will lead me piece by piece to access-less programming now. The show is coming to an end.

    Thank you for all your work and publications – concerning the old web browser control as well as the new one, which I greatly appreciated!