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.

ACCDE files provide significant security especially if combined with password protection, disabling shift bypass, hiding navigation pane/ribbon/application window, using a SQL Server backend etc.
Doing so prevents users importing forms/reports & of course code from another database. However, a major weakness & common complaint is that users can still import all tables & queries including hidden & system tables.
It is possible to make tables 'deep hidden' to prevent this ...but even that can be reversed ...if you know how.
Please add code to prevent this security loophole using VBA (not in the ribbon!). If users lock themselves out by doing so, they only have themselves to blame

In 64-bit VBA hosts, inlined member calls on user objects don't work like on 32-bit VBA hosts.

Given a UserClass with a getter/setter and a Class_Terminate handler (even it is empty).
And in a TestModule a factory procedure returning an instance of this class and also setting the setter.

When I now use this procedure and inline check the value of the getter like in the following sample, it results in a different behaviour compared to 32-bit VBA:

If CreateUserClass(True).TheValue Then

Please take a look in the attached text file for a complete sample:

UserClass.cls:

Private mValue As Boolean

Private Sub Class_Terminate()
'
End Sub

Public Property Get TheValue() As Boolean
TheValue = mValue
End Property

Public Property Let TheValue(ByVal value As Boolean)
mValue = value
End Property

TestModule.bas:

Public Function CreateUserClass(ByVal value As Boolean) As UserClass
Set CreateUserClass = New UserClass
CreateUserClass.TheValue = value
End Function

Public Sub ShortTest()
Const VALUE_TO_TEST As Boolean = True

Debug.Print "Value to check: " & VALUE_TO_TEST

If Not CreateUserClass(VALUE_TO_TEST).TheValue Then
Debug.Print "This is wrong"
Else
Debug.Print "This would be correct"
End If
End Sub

Since 8/1/2018, MS Access has been crashing repeatedly on multiple machines in our office. We are on 64 bit Office 365 and Windows 10. It appears some bug must have been introduced during one of the automatic updates.

This crash appears to occur with automation where I think a second instance of MS Access is calling an MS access program, but not totally sure:

Faulting application name: MSACCESS.EXE, version: 16.0.10325.20118, time stamp: 0x5b64d927
Faulting module name: OLEAUT32.dll, version: 10.0.17134.48, time stamp: 0xebd737a3
Exception code: 0xc0000005
Fault offset: 0x000000000008a283
Faulting process id: 0x32a0
Faulting application start time: 0x01d43fb636a345d3
Faulting application path: C:\Program Files\Microsoft Office\root\Office16\MSACCESS.EXE
Faulting module path: C:\WINDOWS\System32\OLEAUT32.dll
Report Id: b87fac84-eca0-480b-8855-0437a376d7e8
Faulting package full name:
Faulting package-relative application ID:

This crash occurred with conditional formatting in a continuous form

Faulting application name: MSACCESS.EXE, version: 16.0.10325.20082, time stamp: 0x5b524023
Faulting module name: ntdll.dll, version: 10.0.17134.165, time stamp: 0xf4df6dc2
Exception code: 0xc0000374
Fault offset: 0x00000000000f4d1b
Faulting process id: 0x2f34
Faulting application start time: 0x01d42cda8c32b6c7
Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: cd99d3ff-d7aa-4af6-9385-5db23f91f481
Faulting package full name:
Faulting package-relative application ID:

This crash occurs when we click in a combo box and that box is locked and enabled is set to false:

Faulting application name: MSACCESS.EXE, version: 16.0.10325.20118, time stamp: 0x5b64d927
Faulting module name: mso30win32client.dll, version: 0.0.0.0, time stamp: 0x5b5da093
Exception code: 0xc000041d
Fault offset: 0x000000000009b445
Faulting process id: 0x1178
Faulting application start time: 0x01d43fbb05c2f1a3
Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE
Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso30win32client.dll
Report Id: 2d2299db-57cf-42f3-8ced-5cea27393b1b
Faulting package full name:
Faulting package-relative application ID: