FAQ · Modernization and migration

How do you document an undocumented Access database?

Documentation begins with a technical inventory and is completed by connecting database objects to the real business processes they support.

Short answer

Documentation begins with a technical inventory and is completed by connecting database objects to the real business processes they support.

What this means in practice

Object names alone rarely explain the system. Interviews and observation are needed to capture why users take certain steps, what exceptions mean, and which outputs drive decisions.

Inventory tables, keys, relationships, queries, forms, reports, macros, modules, and linked sources.
Map dependencies among objects and identify startup behavior.
Document user roles, recurring tasks, inputs, outputs, and exception paths.
Identify scheduled jobs, external files, integrations, and manual workarounds.
Export VBA for review and establish a maintainable change history.

The practical next step

Good documentation supports repairs, staff training, security reviews, disaster recovery, and migration estimates. It also reduces dependence on the one employee who currently knows how everything works.

This answer provides general guidance. The right recommendation depends on your application, data, users, licensing, and business requirements.