Vinay Garg Assistant Professor

A twenty-year-old VB6 system that still runs the college

UDAAN was written in VB6 and it still processes admissions, fees and SMS notifications. There is a lesson in that.

An old desktop application window titled UDAAN with list rows and a Print fees button

In short

  • Legacy is not a synonym for bad. It is a synonym for load-bearing.
  • UDAAN still runs admissions, fees and SMS notifications for the college office.
  • A backup nobody has restored is a rumour, not a backup.
  • When replacing it, keep the data model, the boring interface and the asynchronous SMS step.

20+ years

UDAAN has run the college office

in production since 2005

Nightly

automated, restore-tested backups

system configuration

1

ledger of every change

audit requirement

The office management system I built for the college — UDAAN — started in VB6, runs on a LAN, backs itself up automatically, and sends SMS to students about their admission status. It is older than most of the students it serves, and it is still the system the office opens every morning.

Why it survived

Not because VB6 was good. Because the system did a small number of things completely, and because every one of those things was boring in the best sense: predictable, backed up, and documented well enough that someone else could fix it.

  • Student records, fees and admission status in one place, not five.
  • Automatic nightly backups to a second machine, tested by restoring them.
  • Automatic updates pushed over the LAN, so no one runs a stale copy.
  • One ledger of every change, which is what auditors actually ask for.

What I would tell a student building the replacement

Rewrite it if you like — the data model is the valuable part, not the language. Keep the automatic backup; a backup nobody has restored is a rumour. Keep the boring interface that the clerk already knows. And keep the SMS step asynchronous, because the day the gateway is slow should not be the day admissions stop.

Legacy is not a synonym for bad. It is a synonym for load-bearing.

Sources

  • UDAAN — in-house office management system, Multani Mal Modi College, Patiala

Frequently asked questions

Is it worth rewriting a working legacy system?

Only if you can name what the rewrite buys. UDAAN still does admissions, fees and SMS notifications correctly; a rewrite is justified by a capability the old system cannot provide, not by the age of its language.

How do you keep a VB6 application safe in 2026?

Keep it off the public internet, on a segmented LAN, with named users rather than shared logins, a tested nightly backup and one machine that can restore it. The protocol is the exposure, not the compiler.

What should a replacement system keep?

The data model, the boring interface the clerk already knows, the automatic backup, and the asynchronous SMS step so a slow gateway never stops admissions.

How do you stop a legacy system from becoming a hostage?

Document the schema, keep one person besides the author who can restore it, and keep the backups tested. The risk is rarely the code; it is that nobody else knows how to bring it back.

Vinay Garg

Vinay Garg

Assistant Professor of Computer Science at Multani Mal Modi College, Patiala. Twenty-five years of teaching web programming, and a habit of building the things I teach about.