I suppose MS Access offers this too, although FM feels more user-friendly, MS Access felt like Internet Explorer 4, where an error dialog would pop-up for every little JavaScript error (disclaimer: this opinion is from 25 years ago).
I suppose MS Access offers this too, although FM feels more user-friendly, MS Access felt like Internet Explorer 4, where an error dialog would pop-up for every little JavaScript error (disclaimer: this opinion is from 25 years ago).
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.
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?
App Script is quite powerful and easier to write and understand than VBA imho.
Untill, a consultant replaced it with an 'enterprise' solution that cost 10000x more to run and maintain.
Sometimes, well designed systems, however simple they might be, would be all that is required.