1507
You have 1 wish... (sh.itjust.works)
submitted 2 years ago by to c/memes@lemmy.ml
87 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 17 points 2 years ago (1 child)

Well, to be fair to Access, it's not like Excel is such a great multi-user database either, now is it? ;-)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 2 years ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    Better yet, put your access backend to OneDrive to acquire an un-openable, un-deletable file.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 years ago

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 2 years ago

    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.

  • permalink
  • fedilink
  • source
  • parent