It still works. That is not the same as fine.
Walk into shops in any Sri Lankan town and you will see the same grey screens: a billing program written ten or fifteen years ago, often by one developer, usually with Microsoft Access holding the data and Visual Basic 6 drawing the windows. Those systems did a real job. Many of them replaced a handwritten book and paid for themselves in a year.
The problem is not that they stopped working. It is that everything around them changed, and they could not change with it.
Signs your shop is on one
- The data lives in a single file ending in .mdb or .accdb, and somebody occasionally has to "compact and repair" it.
- It only runs properly on one old computer, and nobody wants to be the person who changes that computer.
- Sinhala or Tamil names turn into question marks, because the program's controls were built before Unicode was normal.
- The person who wrote it no longer answers, or charges a lot to change a report.
- Getting a list of what customers owe into Excel means retyping it.
- New staff need weeks to learn it, and there is always one person who "knows the trick".
What it is quietly costing
A size limit that does not move
Microsoft's own specification caps an Access database at 2 gigabytes, including everything inside it. Years of bills, stock movements and history creep towards that ceiling, and everything gets slower well before it arrives.
A file that can be damaged by a dropped connection
When one Access file is shared between two counters over the shop network, and especially over wifi, a connection that drops in the middle of a save can leave the file damaged. That is why "compact and repair" became a ritual in so many shops.
Nobody can safely keep changing it
Microsoft stopped supporting the Visual Basic 6 development tools on 8 April 2008. Old programs still run on Windows 10 and 11, but Microsoft's own support statement says it "strongly recommends that you replace your applications with modern technology". Every year a change gets harder to make and harder to find someone willing to make it.
Backups that are a hope
Most of these systems have no automatic backup at all, or a copy kept on the same disk. A failed hard disk or a stolen computer takes years of customer balances with it.
What modern looks like: simpler, not harder
A common worry is that new software means more complicated software. It is the opposite. The power is underneath; the screen in front of the cashier gets simpler.
| Then | Now |
|---|---|
| Scroll a list, or remember the item code | Type any part of the name and the matches appear as you type |
| Separate screens for cash, credit and cheques | One payment panel: cash, card, cheque and credit on the same bill |
| Stock counted on paper, typed in later | Counted with a phone walking the shelves, on the shop's own wifi |
| A backup when somebody remembers | Automatic backups every few minutes, checked by reading them back |
| Reports named like database tables | Reports that answer questions: what to reorder, who owes what, money sitting on the shelf |
| Weeks of training | A new cashier selling within the hour, with the owner's screens hidden behind a PIN |
And it still runs on the shop's own computer, still works when the internet is down, and still prints to the receipt printer you already have. Modern does not have to mean cloud. There is more on that choice in desktop or cloud software.
Moving without losing ten years of history
The fear that stops most shops is losing what is in the old system. Done properly, you do not lose anything:
- Get the data out. Access can export its tables to Excel. Products, customers, suppliers and balances come across; so can past bills, if you want them.
- Check it against the old system. Stock on hand, what each customer owes and what you owe each supplier are placed side by side with the old figures and agreed line by line.
- Run both for a few days. The old system stays available until you no longer want it.
- Train on your own products. Staff learn on the real stock and real prices, not on a slide show.
Six questions about your current system
- If this computer failed tonight, how much would we lose?
- Who can change a report, and how long would it take?
- Can we see today's sales from a phone in the back room?
- Can we get every customer balance into Excel in one minute?
- How long did it take the newest cashier to learn it?
- Does it print Sinhala and Tamil names correctly?
If two or more answers make you uncomfortable, it is worth a conversation. Send us a photo of your current system's main screen, with no customer details on it, and we will tell you honestly what moving would involve. You can also try a modern shop system for yourself in the live demos, with no signup.