I guess you still have to understand locking (especially on distributed filesystems.) I've certainly seen people mess that up with spreadsheets.
I guess you still have to understand locking (especially on distributed filesystems.) I've certainly seen people mess that up with spreadsheets.
Throwing up a database and integrating it into a workflow/system isn't something anyone can just get up and do. I have to imagein you know that.
And if it was manual I am surprised that Excel did not complain about adding more than 65000 rows (or saving more than 65000 rows as XLS). If a user gets a warning about possible data loss they should investigate more.
Of course, there's a bit of a gap between "it's there on the machine" and "we can rely on it for useful work", but baby steps...
MS Access used to come as standard with Office and is actually the perfect solution to many of the problems that businesses use Excel for. It's very rarely that people actually used Access as Excel was far more intuitive and good enough for many projects especially in the early stages.
When people wants a “database” they fire up Excel, start punching in numbers, solar calculators next to keyboard, and use eyeballs to search for strings.
We are able to teach almost everyone how to use complex software like Word and Excel. Why can't we teach people how to use a terminal, SQLite, or how to create a very simple Python script?
And because Excel is "good" for a vast number of use-cases then people use it for everything.