While MS Access is executing code during the object's event, all other events of the object are locked, so they will not be fired.

Let's say we have the Microsoft Calendar Control 8.0 ( mscal.ocx ) placed to a form and we have the code:
Private Sub Calendar1_Click()
Calendar1.Month = 1 + (Calendar1.Month) Mod 12
End Sub

Private Sub Calendar1_NewMonth()
MsgBox "Calendar1_NewMonth event" & Calendar1.Month
End Sub

The sample should displays a message box when the user clicks the control. In MS Access, the message box never occurs, as the NewMonth event is called during the Click event. If the exactly the same code is called on VB6, VB/NET the MessageBox is shown each time the user clicks the control. In conclusion, the MS Access can not handle events inside other events.

I have been able to replicate an error where a form containing only one object - a subform - and no form procedures at all for both the parent and child can crash without warning.

The situation is that the above mentioned form is a search result screen displaying records that match the criteria built in a different form, a search form.

The results form is opened - hidden - the recordsourcethen altered to match the search criteria and a recordset clone is then used to count the records - if the the record count is greater than 1 then I make the results form visible. at this point access then tries to load the designated ribbon for the search results form and after the loading images routine then crashes with only half the form painted on the screen.

The ribbon works and can be used on other screens. The issue only seems to happen when I open the form hidden - set a recordsource - create the recordset clone then make the form visible. I'm guessing a memory issue but feel free to let me know when you find out. The application just crashes with no messages.

I have since removed the hidden and visible lines and the same routine works perfectly.

Sizeable MDI forms in Access 2016 have a single-pixel border that is very hard to grab with the mouse.

The form borders show as a single-pixel whether the form mode is "no border", "dialog", "sizable" or "thin".

One work-around is to make the form a popup form, but if you make every single form in the database popup, you lose the MDI functionality and the ability to have a genuine popup form. When everything is on top then effectively nothing is.

This creates a serious accessibility issue particularly when combined with the fact that MS Access forms and controls don't resize correctly when the Windows text size/DPI is altered.

Changing to the new black theme and then closing out of access completely - re open access and change theme to colorful and the navigation search bar remains black, changing to grey and back to colorful also does not change the search bar back to white.

The black theme is a nice idea and aligns itself with windows themes and visual studio however the implementation leaves a lot to be desired. Disabled ribbon button labels are too dark and don't have enough contrast to be visible. Open a query editor window and try to read the labels in the bottom pane on the left hand side against the white background - this needs to be fixed. Relationship window with the black and white themes especially we are noticing the grey 1 - many symbols are practically impossible to see and the graphics engine seems to be creating horrible tearing when you create a relationship and move one of the tables in the window.