A bit over the top
I've been using Excel for decades. With VBA I might add.
I typically use it to gather together configuration for SCADA projects and then have VBA spit out the SCADA config files (XML etc) at the click of a single button. Easy. Error-free, and the spreadsheet can be a single point of truth - at least in the initial stages before the SCADA system itself becomes the SPoT. Been doing it like that for decades.
Over the years I've seen a lot of spreadsheets that should have been Access projects, but everyone knows Excel, and nobody wants to learn Access. That's a shame because it's a decent tool, too. They're especially powerful when used together, when Access holds the data, and Excel is used to present the data.
Excel is a tool. If you use it for the wrong job then blame yourself or the people that are forcing you to use it for the wrong job. Don't blame the tool.
Biting the hand that feeds IT
