I only allow use of Access for one time projects. Combine multiple tables, query, reconcile or clean up the data, then shut it down.
I've seen far too many live for years as the lynch pin of an org that was all sorts of a pain to connect to in a consistent fashion.
So this is about how I feel:
https://www.microsoft.com/en-us/microsoft-365/blog/2012/08/22/feral-cats-managing-access-databases-in-your-organization/
For a CRM/Ops system, I'm using Dynamics CRM. It can be made kinda like super Access and tailored however. Takes some time, but you can do anything you want to the forms, workflows, etc. Salesforce allows all of the same customization, but since we were already 100% Office 365 and various things linked into that, keeping it all integrated made sense.
So it depends. If you're doing something small for just you or you and a couple people, you could get away with Access I suppose. But if you ever want it to be more than that, you're starting in a bit of a hole.