[rco8786]

No you're right on the money in my opinion. I have very fond memories of spinning up apps in MS Access that were quick and dirty but extremely powerful, and able to be maintained/modified by folks that were not professionally trained software engineers. I think there's a missing area in the market for something exactly like that again.

[rrr_oh_man]

The hive mind really hated (hates?) MS Access and I don't know why.

I built a mini ERP for my father's company when I was 16. Started out as an excel spreadsheet, but then added inventory, accounting, and printing contracts and reports.

He kept using it until retirement and was very happy with it. I could learn & apply SQL. Win-win.

[TMWNN]

I've done that over the last several years, building an order-tracking/accounting system for myself in Excel. (Inventory and fulfillment is handled by commercial software.) I'm mulling over whether to move to a "real" database.

I'm on a Mac so can't move to Access. I've thought about FileMaker, but am considering Panorama X because unlike FileMaker it reportedly allows undoing almost anything, while FileMaker is like the typical database in a record commit not being undoable.

(Yes, I know that not allowing such is good practice, which is why I am not a database admin.)

I've heard good things about Panorama X, and it has a spreadsheet-like UI. However, I've used Excel enough to know that I haven't tapped more than a small fraction of its ability, especially things like Power Query. As much as I loathe VBA, what if the cost of moving to a "real" database isn't the up-front cost or conversion time, but the longer-term inflexibility of Panorama (and, pretty much, anything else in my price range) compared to the beast that is Excel?

[rrr_oh_man]

These days I default to Google Sheets for almost anything.

App Script is quite powerful and easier to write and understand than VBA imho.