borth@sh.itjust.works to Memes@lemmy.mlEnglish · 1 year agoYou have 1 wish...sh.itjust.worksimagemessage-square79fedilinkarrow-up11.03Karrow-down19
arrow-up11.02Karrow-down1imageYou have 1 wish...sh.itjust.worksborth@sh.itjust.works to Memes@lemmy.mlEnglish · 1 year agomessage-square79fedilink
minus-squaresupercriticalcheese@feddit.itlinkfedilinkarrow-up5·1 year agoI only ever encountered Access was once many years ago and I was warned that it had issues with multiple users.
minus-squareZC3rr0r@lemmy.calinkfedilinkarrow-up10·1 year agoWell, to be fair to Access, it’s not like Excel is such a great multi-user database either, now is it? ;-)
minus-squaresupercriticalcheese@feddit.itlinkfedilinkarrow-up1·1 year agoWell 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.
I only ever encountered Access was once many years ago and I was warned that it had issues with multiple users.
Well, to be fair to Access, it’s not like Excel is such a great multi-user database either, now is it? ;-)
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.