I think a lot of the criticism aimed at the Access team lately misses an important piece of context. I've seen people in Forums and such asking why Microsoft is "wasting time" on features like cascading combo boxes, form zooming, large-format monitor support, and other quality-of-life improvements when there are supposedly bigger issues to tackle. But after attending both the MVP Summit and Access Day presentations, it's pretty clear that many people misunderstand how the Access team actually operates.

The reality is that the vast majority of the team's day-to-day work isn't glamorous at all. They're constantly dealing with bug fixes, security patches, compatibility updates, compliance requirements from governments around the world, Office integration changes, Windows updates, and all the behind-the-scenes maintenance required to keep a product like Access alive and functional in 2026. That's the core work. That's what keeps the lights on.

A lot of these newer features that people are criticizing aren't massive corporate initiatives consuming huge budgets and armies of developers. In many cases, they're side projects created during Microsoft's internal innovation weeks, where developers are encouraged to spend time experimenting with ideas they're personally interested in. The Access team actually talked about this openly during the Summit and Access Day sessions. They get one week every year to just work on whatever they feel like. New stuff. Fun stuff. Break it and fix it stuff. Features like cascading combo boxes and form zooming came out of developers saying, "Hey, this would be cool," and then spending some of their own project time making it happen.

Honestly, I love that.

As a developer myself, I completely understand the urge to spend a weekend tinkering with something interesting just because you can. Sometimes those little experiments become genuinely useful features. And in this case, they absolutely are useful. Cascading combo boxes without VBA, especially working properly in continuous forms, is something Access developers have wanted for years. Anyone who's ever had to build that manually with hidden controls and event juggling knows exactly how messy it could get.

To me, these projects are actually a positive sign. They show that the Access team still cares enough about the product to experiment, improve usability, and modernize the platform where they can. They're not just keeping Access on life support. They're still trying new things. And considering how comparatively small the Access team is inside a company the size of Microsoft, I think they're doing a pretty impressive job balancing maintenance work with meaningful improvements.

Could there be bigger features? Sure. Every developer has a wish list. But acting like these quality-of-life improvements are somehow preventing critical work from happening just isn't accurate. Most of the people making those complaints probably didn't attend the sessions where the A-Team explained how this process actually works.

Personally, I'd rather have a team that's still enthusiastic enough to experiment than one that's doing nothing but maintenance mode updates forever. Sometimes the best ideas come from developers simply being allowed to play around with something interesting for a week.

What are some of your favorite side projects that ended up becoming pretty cool? Mine was a little side project where I made video lessons and sold them on CDs. It ended up being kind of a big deal for me... :)

LLAP
RR