Goodmorning MoonNbl
Sorry I've been out of my normal routine the past few weeks
I have dozens of MSAccess frontends running from SharePoint lists so I'm quite familiar with the situation!
]1) An access database file (dot-ACCDB file) will not connect from within a SharePoint document library directly to the Access program, period, drop-the-mic. This sucks as other files such as Excel, Word, PowerPoint will at least open in the Office365 online environment. There is no analogous MSAccess Online program for the file to open to nor is there direct tunnel. I suspect that this is because MS wants us to move to the "cloud" and "power-platform" using their data-verse (whatever it's called today, it's had several names now :) )
]2) What Jimmywick is suggesting will convert the tables in an Access database to SharePoint lists - YOU WILL LOSE ALL TABLE RELATIONSHIPS and there are other issues that may occur with your tables once converted - especially if you have used those nasty little lookup fields at the table level (avoid these at the table level if you can!!)!
]3) You do NOT normally need VBA to transfer the tables to a SharePoint site:
Ribbon>External Data>Export>[More]>SharePoint
If greyed out then
Ribbon>Database Tools>Move Date>SharePoint
In fact, if neither of these are available, or doesn't work, then neither will any of the VBA code (I've been moving some of my databases into SharePoint and PowerApps/PowerAutomate - bit of a learning curve; however, the company isn't installing Access on our newer PCs - why, I don't know, I'm sure it's a licensing thing)
Please tell us a little more about what it is that you're trying to do so that I can help you get your project off the ground.
Please be patient, I'm still out on "walk-about" dealing with some family stuff so my replies will be a bit delayed...
-Z