1510
You have 1 wish...
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Sep 2023
1510 points (98.9% liked)
Memes
45739 readers
507 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
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.
Better yet, put your access backend to OneDrive to acquire an un-openable, un-deletable file.
I actually ran this setup for a pretty long while without major issues. YMMV but OneDrive is not a terrible way to store a single user database backend if you don't have a lot of sequential writes going into it in a short timespan.