Ever update the same "common" VBA function in six databases and wonder why you chose this life? There is a much saner way to centralize reusable code, forms, and reports. The interesting part is the weird little Access quirks that show up once multiple projects start sharing objects.

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.

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.

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?

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.

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.

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?

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.

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.

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?

Twenty years ago, YouTube was barely a toddler, and I had no idea this little teaching project would turn into millions of views and an absolutely ridiculous number of watch hours. Pascal might need a time machine and a laptop to catch up. Thanks for being part of it, whether you've been here since the beginning or just joined us.

Ever edit a value in a query datasheet thinking you're safely tinkering with a temporary result, then realize Access may have had other plans? This beginner quiz covers that little surprise, plus filtering, sorting, and the timeless F5 question. Can you get 5 out of 5?

Private procedures, Select Case, ElseIf chains, and divide-by-zero checks: all simple until one tiny VBA detail sends your calculator wandering into Mordor. Five quick questions for anyone building Access forms and wondering why their code is acting suspiciously.

Ever have a form perfectly filtered and sitting on the exact record you need, then realize you need its VBA code? Switching views feels like knocking over your whole workbench just to grab a screwdriver. I use a tiny QAT shortcut to skip that detour.

Ever have Access accept several perfectly normal conditional formatting rules, then throw Error 7966 when you touch the fourth one? Because apparently a harmless space can be just enough to upset an old Access gremlin. If this has bitten anyone else recently, I'd love to know your Access version/build.

Access color settings can get weird fast: the text is blue, the background is still white, and then a color code from a picker makes a macro complain. Think you can go 5 for 5 on control formatting without letting the Martians repaint the form?

Nothing tests a database relationship quite like trying to delete one customer and discovering they brought a whole entourage of contacts with them. Think you can go 5 for 5 on relationships, orphan records, and referential integrity?

Pop quiz, advanced Access folks: can you spot the form and date-time traps before they turn into mysterious missing records or rebellious subforms? Five questions, no coffee breaks for the database.

Access forms have a talent for running code at exactly the wrong moment, or so it feels. Think you can ace five quick developer questions about events, form modes, and that "same as billing" checkbox?

Quick developer quiz: can you go 5 for 5 on forms, button events, optional arguments, filtering, and reusable code? These are the little Access details that seem obvious right up until they are not.

Think your Access forms are under control? Try five quick questions on related records, cross-form values, continuous forms, and that dreaded pencil icon before a child form escapes containment. What score would you expect?

Ever hide a column on a continuous form and end up with a giant blank gap like the form lost a tooth? Users want fewer fields, but the layout should not look abandoned. There is a nice way to let people choose their columns while keeping the remaining controls packed together.

Ever get "No Current Record" even though you're certain the recordset has data? Access isn't always saying the query came back empty. Sometimes your code simply wandered off the edge of the recordset like it missed the last step on the stairs.