What sustainable support establishes
Known baseline
A versioned copy of source, executable, installer, database schema, configuration and dependencies associated with a known working release.
Reproducible environment
A documented build and deployment process, including OCX/COM versions, 32-bit tools, DSNs, permissions and external services.
Operational boundaries
Critical workflows, acceptable downtime, recovery steps, data ownership and the equipment or users affected by each change.
Diagnosing a failing VB6 application
- Capture the exact symptom, error number and the last known working date. “It stopped after Windows update” is a clue, not a diagnosis.
- Determine whether failure occurs before the first form, during login, on database access or only in one workflow.
- Compare loaded modules, COM class registrations, file versions, registry keys and environment variables with a working machine.
- Test database and network access separately. A provider error may be hidden behind a generic VB6 runtime message.
- Change one variable at a time and preserve a rollback path.
Typical support work
| Problem | Useful response | Escalation signal |
|---|---|---|
| Single-machine startup failure | Dependency and configuration comparison | Failure follows data or user account rather than the PC |
| Lost build capability | Recover compiler, references and binary compatibility chain | Custom controls or source modules are missing |
| Intermittent database errors | Trace connection lifecycle, provider and locking behavior | Data integrity is uncertain; stop writes and preserve copies |
| New hardware or Windows version | Compatibility assessment and controlled deployment test | Kernel drivers, obsolete dongles or 16-bit installers are involved |
When continued support is no longer enough
Repair is sensible when failures are understood and dependencies can still be controlled. Preservation or virtualization may reduce short-term operational risk when the application is stable but tied to an old environment. Modernization becomes necessary when change demand, unsupported interfaces or security constraints exceed what compatibility work can safely contain.
For the broader technology landscape, use the VB6 systems engineering hub. Database faults may require a separate legacy data assessment, while undocumented device communication belongs in the serial engineering workflow.
Information to provide
- Exact error text and screenshots
- Working and failing Windows versions
- Source, executable and installer availability
- Database type and approximate size
- Connected hardware and required continuity window