Yes, but at the time Excel didn’t support concurrency either ;-)
Anyway, you are correct about the issue with concurrent writes, but that’s only because Access was intended as a single user DB.
If you wanted a multi-user DB you should be getting MS SQL server.
Not saying this product strategy worked (it clearly didn’t, otherwise people would not be using Excel), but that’s how they envisioned it to work.
Well excel nowadays doesn’t have issues with concurrent users if you have office 365 like many companies do.
At that time it was Access with the files located at a company shared drive, the issue was concurrent writes I believe.
Yes, but at the time Excel didn’t support concurrency either ;-)
Anyway, you are correct about the issue with concurrent writes, but that’s only because Access was intended as a single user DB. If you wanted a multi-user DB you should be getting MS SQL server.
Not saying this product strategy worked (it clearly didn’t, otherwise people would not be using Excel), but that’s how they envisioned it to work.