Formula 1 chief appalled to find team using Excel to manage 20k car parts

And or access databases.

+7 years ago, heard JPM had +20k of those on their networks. I just shiver thinking about that.

In 20 years I've encountered precisely one Access Database that was very well designed, adequately documented, and implemented correctly - meaning people used a single instance on a specific machine, or Remote Desktop Protocol'd into same.

Connecting to an Access database over a network from individual client apps is a recipe for pain as the database file gets locked, so then people start saving "copy of copy of copy USE THIS ONE" versions and you get divergent database backends with no clean way to merge. IME this always happens for business critical Access systems with no backup and documentation at the least convenient time, and suddenly it's IT's problem/fault. Yes you can connect to a SQL Server backend, but then it's IT's problem/fault/responsibility to maintain, and it takes Access out of the "simple enough for business users" domain.

That said, as a rapid app development desktop tool Access can work very well if you know its limitations. It's somewhat surprising MS never made a 365 web-first equivalent, but that's probably because they'd rather charge for Dynamics 365 licenses and Azure SQL hosting.

I know of no easier way to quickly release a very usable gui on top of a standard relational database then Elixir/Phoenix.

DBeaver has an Excel-ish interface for SQL. The usual rows and columns layout, you can double click a cell to edit it.

You do have to Save to flush the changes to the DB though, and the errors when queries are wrong or whatever are hard to read. Your users will likely be totally unable to grok the errors. I work in IT and it's somewhat difficult for me because of the chain of error handlers (SQL -> Java error type -> Java error -> display to user; there's a lot of Java stuff mixed into your SQL errors).