zlacker

I'm not an MS dev type, but I've often seen these forms questions. What made their forms so easy, or more in general what is so complicated about forms that this was even a tool so many liked?

>>dylan6+(OP)
With Access, a business doing data entry could -- with a business user not a software engineer -- craft a Form and voila, easy onboarding to train new employees instead of filling out sheets of paper and filing them.

>>dylan6+(OP)
MS Access was on its way out by the time I started working in software, but the simplest explanation I can give about why the "forms" question is this, let's say you're a business person and...:

  * You have a huge Excel document that's basically a DB. (What Access kinda was)
  * You want users to interact with said data document, i.e add record, find/query record(s), edit records
  * You add a "form" for users to do just that. You can also add a "login" form to give some users more permissions.

It's basically if you could turn a SQlite file into a low-coded desktop app.

>>znhll+r5
Access is an FE for db — JET Red, specifically.

JET Blue aka ESE is currently used by products like Active Directory and Exchange.

>>dylan6+(OP)
Access biggest advantage by far was that you could share the file on a network drive and having multiple people accessing it: You didnt need any type of complex backup procedure.

In case of failure, just copy-over the old file from yesterday - such simple solutions are pure gold for SME without any big IT department