Platform note
Visual Basic
Visual Basic was a rapid Windows application platform used to build forms-based internal software quickly. It was often chosen for departmental tools, operational utilities, and database front ends where speed of delivery mattered more than formal architecture.
In older estates, Visual Basic can mean classic Visual Basic applications, later Visual Basic .NET applications, or a mixture of both around the same business process.
What it was typically used for
Organizations used Visual Basic for operational desktops, call-center tools, inventory utilities, finance support systems, local administration tools, print and export workflows, and custom front ends layered over Access, SQL Server, Oracle, or file-based data sources.
Why it still matters in rescue work
Visual Basic applications often remain important because they hold business rules that were never rewritten into the larger enterprise systems around them. The risk is usually not the user interface itself, but the logic hidden behind button clicks, screen transitions, and database writes.
Artifacts to inspect when extracting business logic
- Forms and control event handlers: user actions, validation, branching, and process flow.
- Project files and references: external components, DLLs, COM objects, and deployment assumptions.
- Modules and classes: calculations, shared business rules, and integration logic.
- Database access code: SQL statements, stored procedure calls, and transaction behavior.
- Configuration files and constants: environment-specific rules, paths, feature switches, and connection details.
- Third-party controls and reports: dependencies that may carry formatting logic or workflow behavior.
Further reading from Caimito Agile Life
These articles go deeper into knowledge extraction, modernization governance, and the human risk around long-lived Visual Basic systems.