Some companies now prohibit the use of the Legacy Web Browser control available in Microsoft Access because of concerns that security updates are not being sufficiently applied to this older engine. Support for IE Mode in Microsoft Edge or the MSHTML (Trident) engine will continue at least thru 2029. However, many websites are now being designed for the Microsoft Edge browser engine. You may find that opening these web sites throw script errors, render incorrectly, or refuse to render at all with the legacy Microsoft Access Web Browser control. Power BI reports are one example. is an example of a website which displays a nice message “Microsoft 365 applications and services no longer support Internet Explorer 11.” It advises you to “Continue in Microsoft Edge”. The legacy web browser control is based on Internet Explorer 11 MSHTML (Trident) engine. As you may know, Microsoft Support for the IE Desktop application ended. What are the concerning issues for the Legacy Web Browser control? There are several reasons you may want to embed a web browser control in an application. Perhaps you want to make use of showing product pictures that you store on your company website in your in-house inventory application. Or you may want to get information from specific websites to then store and use as data. Or you may want to display data using a web based utility like Google Maps to show addresses or routes, or Power BI to show reports. Microsoft Access has provided a web browser control for your use for many years. In recent years, however, changes in support for the underlying engine for this control have created concerning issues. Do you use the Web Browser control in any of your Microsoft Access applications?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |