Quickly find what's broken — and fix it for good.

Here's a failure I get called about regularly. Nothing changed overnight, but this morning every date field on every form shows #Name?, buttons do nothing, and code that ran for years throws "Can't find project or library". The cause is almost always a broken reference: an Office update or a new machine shifted the version of a library the VBA relies on, and suddenly even built-in functions stop resolving. The fix, repointing the reference and then decompiling and recompiling the code, takes minutes once you know where to look. I've seen offices lose two days to it.

That pattern of dramatic symptom, small specific cause covers most Access troubleshooting. A query that suddenly returns nothing usually traces to one criteria field that changed type, or a join silently dropping rows with nulls. A report printing blank pages tends to be a grouping or Can Grow setting, not corruption. Users overwriting each other's work is a record-locking configuration problem, not "Access being flaky". My first questions are always about what changed: updates, new PCs, a bigger file, an extra user. The answer usually lives there.

When the cause isn't obvious, I work through the layers in a fixed order. File integrity first: does a compacted copy behave the same? Then references and code compilation. Then queries and data. Then the network and multi-user setup. Each layer has quick, non-destructive tests, and every test runs against a copy, so the diagnosis itself can never make your live file worse.

Intermittent problems, the ones that "only happen sometimes" and never while anyone is watching, get a different treatment. Guessing at them wastes everyone's time, so instead I instrument the database: lightweight logging that records who was in the file, what they were doing, and what the error actually said at the moment it fired. Within a week or two the log usually shows a pattern nobody could see from memory, like every incident landing on one workstation, one record, or one time of day. Then it's an ordinary fix.

You also get the finding in writing: what was broken, what caused it, what I changed, and what would stop it recurring. About half the time that last section is a single line, "split the database" or "add a nightly backup", and it's the most valuable line in the report.