Classify the evidence first
| Complete source | Inventory VBP/VBG projects, forms, modules, classes, resources and binary compatibility settings. |
|---|---|
| Partial source | Compare surviving projects with deployed binaries and identify missing controls, libraries and generated assets. |
| Executable only | Map imports, COM identities, strings, configuration, data access and observable workflows. |
Native-code and P-code builds expose different forms of evidence, but neither yields guaranteed exact original source. Form layout, names, comments and build history may be irrecoverable even when operational behavior can be characterized.
Recover an operational model
- Preserve binaries, installers, data, registry state and a known working machine.
- Map OCX, ActiveX DLL/EXE, type-library and native DLL dependencies.
- Trace configuration, database connections, files, printers and device interfaces.
- Exercise representative workflows with controlled inputs and record outputs and side effects.
- Document project boundaries, business rules and uncertain findings separately.
Use VB6 source analysis when source completeness is the main question, executable analysis for technology-neutral binary evidence, COM dependency analysis for object identities, and the VB6 pillar.