Access itself doesn't run on MAC or a phone (unless, possibly you have an old windows phone).

Richard has a video about putting your backend online to be used with multiple windows computers using Access. Access Database Cloud.

To use it from a Mac or a phone, you'd either have to use some remote desktop or perhaps build a PowerApp

Power Apps.

or there is one other way to run it on a Mac, use a virtual machine using software like Parallels Desktop or VMware Fusion. Now my experience with a Mac is a null event.  Other ways as Richard has said is Remote Desktop.  Leaving the host machine on and accessing it that way.  As mentiored earlier for Cloud - See Access Database Cloud.  Or SQL server on the clould and still using the virtual machine for that Mac.  It's just a thought and not well planned out one at that.

I use LibreOffice on my Mac and connect it to my SQL database at home. On Windows, I use Microsoft Access to connect to the same SQL database, and both work great. My thought is that once your database is hosted, you can use either a Mac or a Windows computer to work with the same database.

Donald and Jeffrey have the basic answer right: putting the backend in the cloud does not make an Access front-end usable on a Mac or phone. Access is still a Windows desktop application, so Mac users need Windows somehow, whether that is Remote Desktop to a Windows PC/server or a virtual machine such as Parallels.

Juan's setup can work too, but that is really two separate front ends sharing the same SQL backend. LibreOffice/Base is not going to run an Access application with its forms, reports, VBA, macros, and so on. You would have to build and maintain the Mac side separately.

For phone access, I would normally look at Power Apps, a web application, or perhaps a simple mobile-friendly interface built specifically for the tasks people need to perform. Trying to make a full Access application work on a phone is like trying to fly the Enterprise with a TV remote. Technically, you might get some controls to respond, but it is not the experience you want.

You can fly the Enterprise with a remote, but not fire phasors. Thanks all for the advice.

So true. I have SQL running on my Windows machine, and I use Microsoft Access on Windows. I also built a database in LibreOffice using what I learned from Richard's Access lessons. There is not much difference between the two. So far, I have completed the basics, including tables, forms, and adding data, and I am now working on creating reports.

This is not really a reply, but the conversation brought up a thought.  Is there a way to convert all my VBA into SQL?

Not really as a one-to-one conversion. VBA and SQL do different jobs.

VBA runs in the Access front end. It handles things like button clicks, form events, opening reports, validating what a user typed, displaying messages, and generally controlling the user interface. SQL Server never sees most of that stuff.

SQL Server can handle data-related business rules on the server side. You can use stored procedures, views, functions, triggers, constraints, and so on. For example, if your VBA code performs a complicated update, calculates a value from database data, or enforces a rule that must apply no matter what program connects to the database, some or all of that logic might belong in SQL Server.

But code like this:

"When the user clicks this button, check these controls, ask a question, then open this form or report"

has to remain in the front end. SQL Server has no forms, buttons, reports, or users clicking things.

Think of Access/VBA as the bridge crew of the Enterprise. It interacts with the captain, watches the controls, and gives commands based on what is happening. SQL Server is Scotty down in engineering, storing and processing the data and making the machinery work behind the scenes. You can move the appropriate data-processing work down to engineering, but Scotty cannot fly the ship from the engine room. Well... in some episodes he can... but let me have my analogy. LOL

I am vexed trying to get an online database for my friends without Windows. I was wondering: Microsoft Outlook has a online version, so why not Access?

In the words of Richard.... Microsoft Access is litterally the Red Headed Step Child of Microsoft Office. The icon is red.  As I recall they did try launching Access Web apps in Sharepoint and Microsoft Access online, but retired them because of the complex desktop architecture of Access doesn't translate well to a web browser. It *Access* relies heavily on the Windows Operating System. It would require a complete rebuild for the web (so said a friend of mine that worked with Microsoft many years ago).

That makes sense. Thx.

Yeah, you really need your data in SQL Server or some other web-based database. Once the data is online, you can build whatever front end makes sense for your users: Access for Windows users, a web app for Mac and phone users, Power Apps, LibreOffice, etc.

But Access by itself doesn't work online. Even the Access web publishing tool I'm building now still requires the data to be online in SQL Server. The Access front end remains a Windows desktop application.