Forum Discussion
MS Access crashes with Edge Browser Control Code Builder
Steps:
1. add the ms edge browser control to an ms access form
2. right click on the control choose Build Event
3. choose Code Builder
4. click Ok
5. access freezes then disappears with no error message
6. Event Viewer records the application crash
MS is now aware of the problem. They'll let us know when a fix will be available.
Thanks again for letting us know.
9 Replies
- Dany_ACopper Contributor
Hi,
I'm using Microsoft 365 MSO (Version 2311 Build 16.0.17029.20068) 32-bit.
I'm having the same problem with the Edge Browser.
In fact, the crash occured when the browser is set to Visible = False and you open the form.
If you set Visible = true, the form will open normally.
Please let us know if you have a solution for this issue.
Hi,
> Version 2311 Build 16.0.17029.20068
There's been a fix for a related (?) problem in the latest 2311 build 17029.20108. So, you can try to update and check whether it also solves your problem.
If not, do you do anything in code, like navigating, setting it to visible etc. when you open the form?
Servus
Karl
****************
Access Forever
Access News
Access DevCon
Access-Entwickler-Konferenz AEK
- George_HepworthSilver Contributor
Check out the Access Forever article. Please add your description of the problem there, as well.
I'm also going to pass this along to see who else can replicate the problem.
- George_HepworthSilver Contributor
I can replicate that with Access 365.
What version do you have? I have Version 2306 Build 16529.20146 installed.- thomas9246Copper Contributor
George_Hepworth I am running MS Access version 16.0, build 16501.
- George_HepworthSilver ContributorThanks. We've replicated this a couple of times now. It's been forwarded to the MS Access team for evaluation.
The workaround that I found is to immediately use the Build Event which automatically pops up when you first insert the web browser control. At that point, it accepts the URL without crashing. If you dismiss the dialog, but go back later, following your described steps, then the crash occurs.
In my case, the VBA IDE flashed before the crash. Did that also happen in your scenario?