Yes, I’m being cheeky here, but I thought I’d point out that we’ve long since celebrated this phenomenal bug‘s 2nd birthday (was actually around June 1st, perhaps even end of May) and still no fix!

Furthermore, the last update on the subject from Microsoft was Nov 29, 2019!

I love the Access Team, I truly do, but this situation is out of control.

Let’s keep our fingers crossed it won’t be another 2 years before this is actually fixed.