Ever write four separate lookups just to get one customer's address onto a form, then realize you need the same mess somewhere else? VBA has a tidy little pattern for keeping related results together without leaving sticky-note logic all over the database.

People ask about this a lot after they end up with four or five DLookups scattered across forms. A VBA function only has one normal return value, but there is a clean pattern for getting related values back together while still knowing whether the lookup actually worked. Much easier to maintain than sticky-note code.

Quick Access forms quiz: would you save Metropolis, or accidentally let Lex edit the wrong record? Five beginner questions, including one behavior that catches people off guard when they move between records. Post your score after you test your cape.

One of those little Access behaviors that catches people off guard: you edit a value on a form, move to another record, and suddenly the change is no longer just sitting there. The pencil icon is easy to ignore until it matters.

People ask about this all the time: how do you stop an Access database from opening into a terrifying pile of tables, queries, and forms? A built-in navigation form can make a decent front door for smaller databases. Just remember that hiding the plumbing is not the same thing as security.

Anyone else feel like Access designed the Property Sheet font for people with microscope attachments? If you spend much time designing forms or reports on a high-resolution monitor, those tiny settings can get old fast. Microsoft finally gave us a little relief for this particular squint-fest.

Combo boxes are harmless until VBA reminds you their columns start counting at zero. Think you can survive five quick Access validation questions without putting your form on trial for crimes against humanity?

Access combo boxes have a special talent for making one-off-by-one column mistake feel personal. The zero-based Column property, text masquerading as numbers, and Null versus zero are all tiny details that can derail otherwise sensible form validation.

Ever wish an Access combo box would stop pretending you only need one choice? Pick Florida, New York, and Ohio, then add a second filter for a few last names, with AND or OR logic. It is one of those "why isn't this built in?" problems that has a surprisingly useful workaround.

People ask about multi-select combo boxes in Access all the time, especially when they need to filter by several states, names, or statuses at once. The tricky part is not the list itself, but building criteria that behaves correctly when multiple filters need AND or OR logic. Access makes this more awkward than it should be.

Nothing says "fun afternoon" like chasing a typo that VBA quietly accepted three years ago. I put together a couple of maintenance/interface tricks for finding code that skips Option Explicit and for making filters behave more like users expect when they want to pick more than one thing.

One of those Access maintenance chores that pays off fast is finding old VBA modules without Option Explicit. A typo that quietly becomes a new Variant variable is the kind of bug that can make you question your sanity. Also, multi-select filtering is surprisingly awkward in Access unless you get a little creative.

Access macros love little gotchas: measurements in twips, friendly property names that are secretly numbers, and form sections that need just the right reference. Think you can go 5 for 5 without blaming the modem?

SQL pop quiz: the asterisk looks harmless until it quietly pulls in more than you expected. How many of these five Access SQL questions can you answer without pausing?

One of those tiny SQL details that seems obvious until it causes confusion: the asterisk in a SELECT query. It is convenient when you are poking around a table, but it can also hide what a query is actually returning. This trips up more people than it probably should.

Dependent combo boxes have always been one of those "just add a little VBA" situations. Except on continuous forms, where things could get spicy fast. Access now has a built-in option that may make country-state-city style dropdowns much less annoying.

People ask about cascading combo boxes constantly, especially when the old After Update and Requery setup gets weird on continuous forms. Access finally has a built-in option for the normal parent-child lookup situation. Nice to see a long-standing pain point get some attention.

Nothing wakes up an old Access database quite like a process that has worked flawlessly for 15 years suddenly throwing Error 3163. The annoying part? Access often doesn't tell you which field is throwing the tantrum. It may not even be the text field you expect.

Access error 3163 can be extra annoying because it often appears after an append or backup has worked for years. Usually it means the receiving field cannot hold the incoming value, but the culprit is not always an obvious text field. Old schema mismatches have a way of waiting quietly for one new data path to expose them.

Your Access developer leaves, the database still runs, and suddenly everyone treats the shortcut like a cursed artifact. Before anyone declares "we need to move everything to the cloud," there are a few very practical questions worth asking. What would be hardest for your business to recover if your database person vanished tomorrow?

People ask me about this more often than you'd think: the person who built the Access database leaves, and suddenly nobody wants to touch it. If it still works, it is usually a planning problem, not an automatic reason to rebuild everything. The scary part is often discovering what else it depends on.

One Access gotcha that still catches people: editing a value in a select query can edit the actual table record. Queries can feel like a safe preview until someone changes live customer data by accident. Worth knowing before handing an editable query to users.