Access Releases 7 Issue Fixes in Version 2311 (Released November 25th, 2023)

Thank you for this. Not sure if it's been reported to the team yet or not I'm sure it has I probably just haven't seen it but I'm experiencing an issue where if I am working with the new Edge browser control and I go into the Visual Basic editor if I select the browser control from the drop-down on the left and any of the events from the drop-down on the right then Access crashes and it happens every time on multiple machines.

Hi Richard,

I think you will find that if you choose an event (such as KeyDown) that is supported by the Edge Browser control, then it will not crash.  If you choose an event that is not supported by the control, then it will crash.

We will definitely fix this (the events that are not supported should not appear in the list, but even if they were there for some reason, it should not cause a crash).

Look for this fix for this in an upcoming bug blog.

Thanks for the report.

Shane

Hi Shane. Thanks for replying. The browser control will crash Access immediately if you add it as a control on a new form and go right to the VB editor and pick the control from the list. Easier to show you: Edge Control Crashing Access

Let me know if you have any questions or need any more info from me.

RR

Yes, that's because it picks the first event in the list (AfterUpdate).  If you choose Build Event from the context menu in form design, it will select the control with the DocumentComplete event selected, which won't crash, since it is supported.

Shane

That would definitely explain it. Thanks. 🙂

Many thanks for all of these fixes, four of which I recognise as I reported them recently and all affect me directly.

1. I will update my article on reserved errors to mention the -1001 fix for reserved words in SQL View queries.

2. As you already know I'm very grateful for being finally able to open queries directly into SQL view. I'm now just waiting for that feature to be added to the Create ribbon as well

3. The recent fix to the Edge browser control bug was also very welcome

4. I'd also just like to mention the very prompt fix to the recent font display bug. Reported on a Friday evening & fixed the following Monday. That was very impressive!

It really is important to release these notes earlier. Over the last two weeks I have had two different client applications crashing whenever a form containing the Edge Browser control was opened. It coincided with the release of office V2311 but the official release notes did not list any Access changes and had no mention of the Edge Browser control.

I have managed to isolate the problem to the following:

If a form does something with its recordset in the Open or Load event handlers, it is forced to do a sort of "double-load". This allows it to completely load in the background during the initial Load event so that it may complete the recordset operation. It then proceeds to run the later event handlers. This behaviour can be observed by multiple occurrences of the form's Current event and events within any subforms, first during the premature load invoked by the Load event, and then again when the Load event has completed and it there own turn to run.

If the form with this behaviour contains the modern web browser control and the version is V2311, Access crashes. The web control does not need any code, merely its presence causes the crash.

Neil

There were issues with the web browser in v2311 which were caused by external factors unrelated to changes in either the browser control or Access itself. AFAIAA, these were fixed in v2312 though I do still have one app with an Edge browser control that is still causing me issues in v2401.

You may find this thread useful: Edge Browser window keeps freezing/crashing after interacting with VBA. | Access World Forums (access-programmers.co.uk)

Colin,

The trouble is V2311 is still the current release (current channel). So even if it is fixed on the insider programme, my clients will have to wait.

For now, I have had to disable the browsing function and remove the bad control from the application. The first time I saw it, it could have been due to Windows 11/10. Then a second client's app died and I suspected V2311. Then my own development PC updated to V2311 and it also died.

It would have been nice to have had the release notes on time to have been able to substantiate my hypotheses that is was a bug in MS365 and not my application. It would also have saved me several hours of debugging. A three week delay is simply not acceptable.

My application is way too complicated to be used as a demo, but I did manage to distil the problem down to the nested event procedure behaviour I describe. Do you need me to provide a demo database exhibiting the problem? It will have to wait for the New Year though.

I would expect v2312 to be released next Tues/Wed so suggest you recheck when the update is available.

In the meantime you could try temporarily moving to an insider' channel such as Current Channel Preview so you know what to expect.

Also, if you want, I can email you the database I was using in that thread at AWF for you to test.

Whilst I agree that it would be much better if the list of bug fixes was published at the same time as the update is released that wouldn't have helped help in this case. These bug fixes are not release notes. For release notes, go to Release notes for Current Channel releases - Office release notes | Microsoft Learn

However, in this case, you won't find anything listed for Access. As mentioned, the browser issues that I'm aware of weren't due to changes in Access itself.

If the issue still exists in v2312 then a demo database together with an explanation could provide useful info for me to forward to the Access team