Access gets a fair bit of criticism.
It’s old. It doesn’t scale. It isn’t suitable for serious business systems.
Except I’ve come across Access systems that have been quietly running businesses for 10, 15, even 20+ years.
Usually, Access isn’t really the problem.
A database might have started life as something fairly simple, built to solve one particular problem.
Then the business grows.
More people start using it. More data goes into it. New features are added. It gets connected to other systems. And before you know it, that little database has become something the business depends on every day.
Eventually it starts getting slow or unreliable and somebody says:
“We need to get rid of Access.”
Maybe.
But before doing that, I’d want to understand what’s actually causing the problem.
We’ve taken existing Access applications, moved the data into SQL Server, improved the code and queries, and made them faster, more reliable and easier to support.
The users can carry on using the screens and processes they’re familiar with, while the system underneath is considerably stronger.
And if the business needs browser access or a mobile app, those can sit alongside it too.
Sometimes replacement is absolutely the right answer.
But if an Access database has been running an important part of your business for 20 years, I’d be reluctant to throw away 20 years of knowledge without having a proper look at it first.
Old software isn’t necessarily bad software. Sometimes it just needs a bit of attention.
Originally posted on LinkedIn.