Also, things are often not as binary as mere love and hate.  There are often a mixture or gradation of various sentiments.  You love Access, but you also have a list of evil Access stuff, for instance.

Yeah, I saw your comment on YouTube earlier. I would love to have a back-and-forth with some people that hate Access. Some of their complaints are justified, like when they say that Access doesn't work online. That's absolutely true - Access wasn't built as a web-based database. But on the desktop, it can't be beat.

So sure, I would love to have a friendly debate with some Access haters. I'll post that on your YouTube comment and maybe I'll mention it in the next Quick Queries too.

Yeah, it's possible to hate certain things about something that you love. For example, I love Star Trek, but I hate Discovery. I love Rush, but I hate The Speed of Love and Virtuality. They can't all be winners. LOL.

Regarding the reasons mentioned in your video ("lost of control," "corruption horror stories," etc.), are those from people who have actually had first-hand experiences instead of just hearing it from someone else ("Oh, my brother's friend's former roommate said his Access DB was corrupted...").  Not to say those reasons aren't valid, but if they aren't backed up with substantive background info, they have little merit.  When I see random Internet comments with no detail, I dismiss it totally.  We could only have a meaningful discussion on this topic if we actually had good info.  We should start with the questioner in your video.  He really should ask his IT people point blank, what exactly they don't like about Access?

For instance, in the early 2000s, I migrated from Access to SQL Server backend and web front end because our company needed online usage, and also not all our users could use Access, but almost everyone could use a web browser.  This is the kind of specific info we should be looking for.  There was no outright like or dislike on my part, and I still continued using Access in some capacity.  The true worthiness of Access is not that clear cut, as we know, so we need to hear from different perspectives that have substantive info.

To quote Zula from Conan The Destroyer: "Who cares who's sister's brother's cousin it is? What difference does it make?"

Sorry... couldn't help myself.

I'll reach out to the original person who emailed me and see if they have any concrete feedback. Honestly, this one just came from my grab bag of emails. I've got a "would make a good video" folder in Gmail with thousands of messages, and I often pull random ones to spark video topics. But you're right, I hear these same complaints over and over, so it would be worthwhile to dig deeper and get some specific comments from Access users.

And of course there's this one: "I am your father's, brother's, nephew's, cousin's, former roommate."

Databases are going to corrupt. Especially badly created ones. Prior to my entry into Access, I played with Parados, DBase, FoxPro, and a few others.  Push them hard enough and they got corrupted. I avoided Access for the longest time because my understanding of SQL, or lack of. I didn't want to learn yet another language. Paradox for windows had memory leaks and I was told Access was no better. I was starting to head towards MYSQL (wait my understanding of SQL was non existant) but we were trying to set some of our office stuff online.  My first online attempt was using ASP and some database done in... get ready for it Access.