Good news! This has been resolved in Access version 2501. After the MSOffice update on 28th Jan the issue is now fixed.