Good question. What I meant was, if you are a solo developer and you are disciplined enough to always keep your logic organized - for example, using public functions consistently to manipulate your data - then you do not really need class modules. You can build perfectly fine, professional Access databases without them. But even someone like me, after 30-plus years of doing this, sometimes takes shortcuts. I might hard-code a quick workaround, and if I am not careful, that logic can get spread out all over the place.

Class modules help prevent that by forcing you to centralize your logic and control access to your data. They keep you more disciplined, even when you are tempted to be lazy. So in short: if you are already extremely disciplined and consistent on your own, you might not need classes, but they still make a lot of things easier, safer, and cleaner, especially as projects grow larger.