MS Access for Internet sharing among Users

Take a look at the various options presented in https://www.devhut.net/access-back-end-location-wan-online-server-onedrive-dropbox/ (see the section entitled 'What are the Alternatives Then?')

That said, SQL Server/Azure are great options. I personally would have resolved the small issues if I had access to such a system.

That all said, if I need to run a system and share it over the Internet, I use Web Technologies: .net, PHP, ... There is simply no comparison! Each has it's purpose.

I've gone over the article. No solution is proposed. All proposed solutions in the articles are not practical.

I don't know what to tell you at this point.

SQL server doesn't work for you. The other well known solutions mentioned in the article (SharePoint, Azure, Terminal Services, Citrix, RDP, ...) all don't work for you.

I guess you're out of luck then.

There are many ways to share desktop Microsoft Access for multiple users' simultaneous access.

Access apps are not easily shared for simultaneous access except when all users are on a LAN. As soon as you have users who cannot access the LAN, you have problems.

The best solution I have encountered for that scenario, is to have one or more PCs that remote users can log into and then run an Access app from that remote session. A similar solution is using a Terminal server (like Citrix). But that is more expensive.

Another solution is using a data source in the cloud, like Azure. An Access front end can be setup to link to such a clud Datasource.

You are probably not going to like any answer, then. If low-cost is the driving factor here, it eliminates some of the more viable options.

You can enable remote users to log in via RDP type technology. That can be done, but it does cost money to set up and manage.

Microsoft Access is a Windows application that runs only under a Windows operating system. That also limits your options. Each user has to have a computer on which to run their copy of the application, and that eliminates the possibility of a browser-based approach. Well, there are some companies offering that as a service, but again, licensing costs are a factor.

You've already rejected the one approach I would consider most likely to prove appropriate because it would require you to learn and adapt techniques and approaches to exploit to the client-server architecture of an Access/Azure SQL or Access/SQL Server deployment. That further limits your options.

One other option would be to look at using SharePoint lists for the data. It's doable, but a recent thread here in which another person struggled with some of the nuances involved in setting up a basic Access/SP deployment suggests it's not something one would tackle without adequate preparation and study. You can do that, but it requires time to prepare. Also, you need to have a M365 site to support the SharePoint lists.

Here's a YouTube video that gives an excellent overview of that approach.

https://youtu.be/Uw6JBJfcjCo?si=vTB--Z5nG4G7XTqm

Depending on the environment in which you are deploying this application, perhaps your users would be amenable to some sort of licensing.