Map the complete dependency
- Identify MDB version, Jet/ACE provider and DAO or ADO usage.
- Inventory linked tables, workgroup files, passwords and external paths.
- Trace saved queries, schema assumptions, indexes and application-generated SQL.
- Record network sharing, lock-file behavior and concurrent-user limits.
- Locate validation and business rules implemented only in VB6.
Preserve or migrate
Preserve a stable deployment when the data remains healthy and concurrency is controlled. Migrate the database separately when provider support, scale or network reliability is the main risk; change the application only after query and transaction behavior is characterized.
Use MDB recovery for damage, DAO diagnosis, database modernization and the VB6 pillar.
Provide application/source, MDB and linked assets, connection configuration, user count and representative workflows.