Still running the business on Microsoft Access?

Still running the business on Microsoft Access? An Access database someone built fifteen years ago may still be doing its job well. The question is whether it's holding the business back, and that usually shows up in a few specific ways.

Why Access databases last so long

Access was the tool a capable office manager or a nephew who "did computers" could use to build something genuinely useful: customers, jobs, stock and a few reports, all in one file. It fitted how the business worked because someone inside the business built it. That's why so many are still running.

The weakness is the same thing. It was built by one person, rarely documented, and it lives in a file on a shared drive or a PC in the corner.

Signs your Access database is holding you back

The first sign is usually people. Only one person understands the forms and queries, and everyone is quietly worried about the day they leave. Changes wait for them, and nobody else dares touch the design.

The second is access. Your team wants to update a job from site or from home, and Access is a desktop database. Microsoft retired Access web apps years ago, so getting the data onto phones usually means remote desktop or copying things into another tool.

The third is reliability. Several people working on the same file over a network drive is where corruption tends to creep in, and an Access database file is capped at 2GB. If "compact and repair" is part of your weekly routine, or you've split the data into yearly files to stay under the limit, the database is telling you something.

And then there's everything around it. Invoices get retyped into the accounts package, customers email in and someone copies the details across, and reports are exported to Excel to be fixed by hand.

Your options

Keep it and make it safer. If it works and the team is small and office-based, you can split the front end from the data, move the data into a proper database server, back it up properly and document it. This buys time, but it doesn't fix the one-person problem or give you mobile access.

Move to an off-the-shelf product. If your Access database is really a jobs, quotes and invoices system, a ready-made product may cover most of it. For trade and service businesses that's what TradeOps, our own platform, is for. Customers, price lists and open jobs can be brought across from exports and spreadsheets, and the website sits in the same system. The catch with any product is that the odd, specific things your database does may not survive the move.

Rebuild it as a web application. When the database encodes how your business actually works, with its own rules, pricing and reports, the right move is usually to rebuild it properly as a web app with a real database behind it. It's the same logic, but it runs in a browser, on phones and from anywhere, with proper user accounts.

How we'd replace an Access database

We start by reading what you have: the tables, the queries, the forms and, most importantly, the reports people actually use. That becomes a written plan. The first release covers the screens the team uses daily and is a few weeks of work, priced after a scoping conversation. We move the data onto a copy first and check it against the old system before anyone switches over.

You own the code, the repository and the cloud account from the start, and it's hosted in UK or EU regions by default. More on how we work is on our software development page.

Quick Comparison

• Keep and harden Access: the lowest cost and least disruption. Best for small office-based teams where it still works. It leaves you with one expert, no mobile access and file limits.
• Off-the-shelf product: quick to adopt, and someone else maintains it. Best when the database is a standard jobs-to-invoice system. You may lose the custom rules it grew over the years.
• Rebuild as a web app: keeps your processes, works anywhere, and you own it. Best when the database is how the business runs. It takes longer to start and needs ongoing care.

Which one do you need?

If Access works and the person who built it isn't going anywhere, tidy it up and leave it alone. If you're a trade business whose database is really quotes, jobs and invoices, look at a product first. If you're still running the business on Microsoft Access because nothing off the shelf fits how you work, that's the case for a rebuild. Replace it on your timetable, not the day the file won't open.

If you'd like a second opinion, send us three or four sentences about what the database does and who uses it. We'll tell you honestly whether to keep it, replace it or rebuild it. Get in touch with Eight Mile.