Modernizing a VB6 Application Your Business Still Depends On

A Visual Basic 6 application is modernized by rebuilding it on a current platform, usually as a .NET web application, while the old system keeps running. The business rules inside the VB6 code are extracted and preserved, the data moves to a current database, and users switch over once the new system matches the old one. Line-by-line conversion tools rarely produce software worth keeping.

Signs this is your problem

• The application will not install cleanly on new PCs.
• A Windows update broke a screen or a report.
• You keep an old machine running because the software needs it.
• The developer who wrote it has retired or cannot be reached.
• Staff want to use it from home or on a tablet and cannot.
• Changes you need have been “too risky” for years.

Why a working VB6 application is still a risk

The honest position is that your VB6 application probably works fine today. That is exactly why it has lasted. The risk is in everything around it.

• The development tools are long out of support. Microsoft ended support for the Visual Basic 6 development environment in 2008. Windows still runs VB6 programs, but the tools used to change them are from another era.
• The parts it relies on are orphaned. Most VB6 applications use third-party controls from vendors that no longer exist. When one breaks on a new version of Windows, there is nobody to call.
• The people are retiring. Fewer developers each year can read VB6, let alone change it safely.
• It is stuck on the desktop. No browser access, no phones, no easy way to connect it to anything modern.
• It complicates security and insurance reviews. Software that cannot be patched is hard to defend in an audit.

Your options, honestly

Leave it alone. Reasonable if the application never needs to change and the business would survive losing it. That is rarely true of a system people use every day.

Run it through a conversion tool. Automated converters turn VB6 code into .NET code that looks like VB6. You get old design on a new platform, and it is still hard to maintain.

Rebuild it properly. The VB6 application becomes the specification. Its screens, rules and reports are rebuilt as a modern web application, improved where your people have wanted changes for years. This is what we recommend for systems the business depends on.

What happens to the business rules buried in the code

Twenty years of decisions are written into a VB6 application: how a price is worked out, what counts as a valid order, who may approve what. Much of it is documented nowhere else. The first job in any modernization is to read that code and write those rules down in plain English, so they are carried forward on purpose and not lost by accident.

How Keene Systems handles it

1. We assess the application and its source code. You get a plain statement of what is there, what condition it is in and what the sensible path is.
2. We document the business rules. So nothing important depends on anyone’s memory.
3. We rebuild in stages on ASP.NET Core and SQL Server. The parts that matter most come first, and you use them as they are finished.
4. We migrate the data and switch over. The VB6 system keeps running until the new one has proved itself.

The next step is a short, no-pressure conversation. Book a call with Lance Keene or use the form on this page.