You don't have to wait on them for that! People like Ken Getz provided all the necessary code to adjust forms, controls, ... based on the screen resolution more than 30 years ago. I know it's not baked into Access, but it's just a question of copying a module and calling a function. www.devhut.net/access-form-resizing-based-on-screen-resolution/ And since it's not on the roadmap I wouldn't hold my breath to it such an improvement in the near future. I'd suggest starting a suggestion in the Feedback Portal. I know there used to be one on UserVoice for this very feature request, but I don't believe it was copied over when they made the switch to the Feedback Portal. I do agree however, this is 20+ years overdue, but at least people like Ken shared the solution to the problem.

Glad you liked it.

4 worker bees. I broke it down in my blog article: www.devhut.net/new-access-product-manager/

Sadly, Access has a smaller development team. If you watch some of the KZfaq videos in which the Dev Team has participated you'll notice over time that their team has changed, so knowledge retention is probably an issue as well. Beyond the staff, how many product managers have we had 4-5. No stability at the top impacts vision, motivation, ... I was taken back when we got a new product/program manager who publically explained that Access gets 1/4 of her time because they manage other projects (who says that publically!). That, right there, demonstrated the importance Microsoft's management put on the product! There also the whole PR side of things where Access is omitted from texts/descriptions, menus, icon/lists and is never advertised. It's been brought it up I don't know how many times over the years and nothing ever changes. Then add to that ignoring user feedback for decades now, releasing more bugs than one person can keep track of, releasing unfinished 'features' (modern charts, modern web browser, ...), investing the few resource they have in web databases, for instance, only to abandon the whole thing a few years later after people invested in that feature, ... Killing love features ADP, pivot ... What I've noticed in 20 years of development is a lot of flip flopping from Microsoft and wasted investments on useless things while ignoring true database elements (SQL editor!) which would have moved the product forward. Look at the way the roadmap wasn't updated for at least 7 months. Look at the Feedback Portal. Look at the Fixes and Workarounds page. All of the elements show a trend, an overall approach of mediocrity. Do all sorts of things, but don't do any of them properly and then leave them collect dust and don't maintain them. The subject here is vast and one which isn't likely to ever be resolved. It's a cultural corporate issue. It would require Microsoft care enough to invest in the product again and clean things up. I could go on and on, but I'll stop here.

@@DanielPineault Really great write up and very interesting thoughts!!! Thank you for taking the time to write this and for advocating for us MS Access users :)