Are you, or were you ever, a Microsoft Access developer? Don’t be shy. No one’s going to judge you.
Back in the day, when dinosaurs roamed the Earth and small departments were pushing Excel spreadsheets to the limit, someone would eventually ask, “Why aren’t we using a database for this?”
“We have Excel.”
Fair enough. Excel is a wonderful tool. You can start with an idea, put some information into rows and columns, add a few formulas and have something useful before lunch. It gives people who understand a business problem a way to work through it themselves.
Then the spreadsheet becomes useful to someone else. A few columns are added. Another department needs a copy. Before long, a workbook that started as one person’s tool is supporting a process that several people depend on.
That is often when the questions become more interesting.
One product is easy to see
I had a client that managed its product-development process through spreadsheets. At any given time, there might be 300 to 400 SKUs at different stages of their lifecycle. The statuses included What If, Project Active, Inactive and Dormant.
Each product spreadsheet contained rich information: its brand and supplier, costs and expected selling prices, descriptions in multiple languages, bills of materials and development milestones.
There was real value in those files. People had put thought, experience and effort into them. Open a spreadsheet and you could learn a great deal about that particular product.
But there were many products, many spreadsheets and different versions of those spreadsheets. Which version was current? Where should someone look for the latest information? How would everyone know that a change had been made?
Then came a perfectly reasonable company-wide question:
“Can you show me all our active products, grouped by brand, with their costs and expected selling prices?”
The information was there. It was just spread across hundreds of files. Each spreadsheet could tell us about one product. The business needed answers about all of them.
When related information needs to work together
You can do a great deal of consolidation and analysis in Excel. The question is how much effort the business should spend repeatedly assembling information that belongs together in the first place.
A database gives that information a shared structure. A product has a record. Its brand, supplier and development status have consistent meanings. Related information, such as the components in its bill of materials, can be connected to it without squeezing everything into one enormous worksheet.
Now the request for active products by brand has a clear starting point. The criteria can be defined once and used again. A different question can draw on the same records.
That still requires decisions. What makes a project active? Who maintains the cost? Which selling price belongs in the report? Moving information into a database does not settle those questions for you. It gives you a practical place to apply the answers consistently.
This is where someone who understands the business can make a real contribution as a developer.
Access was a great place to develop a developer
Microsoft Access brought tables, queries, forms, reports and automation together in one environment. You could organize information, ask questions of it, give people a form they could use and turn the answers into a report.
For someone close to the day-to-day work, that was a powerful invitation to start building.
You learned to think about relationships, rules and exceptions because real people needed the application to handle them. A request for “one more column” could lead to a useful conversation about what that column meant and where its value came from.
Some of those departmental applications went on to serve their organizations for years. Along the way, they accumulated more than records. Their queries, calculations and reports captured decisions about how the business worked.
That history deserves some attention before we decide what comes next.
Understanding what we already have
An established Access application may still have plenty to offer. It may also need changes. Either way, understanding the information and business logic inside it is a sensible place to begin.
That is part of the thinking behind Karris Insighter for Microsoft Access, or KAI. It helps make an Access application’s recorded structure and logic easier to explore through clickable documentation. In the next article, I’ll look at how that understanding can help us get more value from the applications we already have.
Join the November 10 KAI session

Tuesday, November 10, 2026, at 6:30 p.m. Central / 7:30 p.m. Eastern. Free on Zoom.
I’ll also be demonstrating KAI with Access User Groups on November 10, 2026. If this sounds familiar, you’re welcome to join us. Event details.
My thanks to Juan Soto, Access User Groups and IT Impact for helping bring this session together.
For now, which spreadsheet in your organization has quietly become a business system?
