Quick Queries #98
By Richard Rost
2 days ago
Why Is Microsoft Access Not Available For Mac? In Quick Queries 98, we will address why Microsoft Access has never had a native version for Mac, discussing both the technical challenges and business decisions behind it. We will look at the best ways Mac users can still run Access today, such as using Parallels, VMware, or Remote Desktop. We will also talk about Power Apps licensing, options for connecting to SQL Server and MySQL, converting Access forms for web use, using Google Forms for surveys, and some recent updates to Access and related community feedback including questions about the Office color palette and website design. PrerequisitesLinksRecommended CoursesUp Next
Keywords TechHelp QQ Quick Queries, Access for Mac, Parallels Desktop, run Access on Mac, Power Apps, SQL Server connector, Access web converter, SharePoint lists, Google Forms prefill, Power Apps licensing, premium connector cost, FileMaker Pro, ODBC drivers, ActiveX, VBA integration
Intro In Quick Queries 98, we will address why Microsoft Access has never had a native version for Mac, discussing both the technical challenges and business decisions behind it. We will look at the best ways Mac users can still run Access today, such as using Parallels, VMware, or Remote Desktop. We will also talk about Power Apps licensing, options for connecting to SQL Server and MySQL, converting Access forms for web use, using Google Forms for surveys, and some recent updates to Access and related community feedback including questions about the Office color palette and website design.Transcript I never wonder why Microsoft Access has been available on Windows for literally decades, but there is still no native version for the Mac. Welcome to another TechHelp Quick Queries video brought to you by Access Learning Zone. I am your instructor Richard Rost. Today, we are going to talk about why Microsoft never released a Mac version of Access, whether it is because of technical limitations, business decisions, or a little bit of both. We will also look at the best ways that Mac users can still run Access today if they need it. We have got more questions from YouTube, my website forums, emails, and lots more covering Microsoft Access, so let us jump right in.
Today's question comes from Miguel from Baton Rouge, Louisiana, one of my gold members. Miguel says, I have been a Mac user for years, but I keep a Windows laptop around just for Microsoft Access because that is what we use at work. Your work is smart. I have always wondered though why did Microsoft make Word, Excel, and PowerPoint for Mac, but never Access? Is there a technical reason or was it just a business decision?
The short answer is that Access was never really designed to be just another Office application. It is really a complete database development platform. It is not as simple as a word processor or a spreadsheet. If you know Access, you know, inside the Access file you have got tables, queries, forms, reports, VBA code, macros, automation, and all kinds of other objects working together.
In my opinion, the biggest reason is technical. Access was built from the ground up around Windows technologies. It relies heavily on things like the Jet and Ace database engine, COM automation, ActiveX, VBA integration, the Windows API, ODBC drivers, and a whole bunch of Windows-specific plumbing. It is not something Microsoft could just simply recompile for macOS like a common application. They would basically have to rewrite huge portions of the product from scratch.
There is also the business side. Access has always been strongest in Windows business environments. By the time Macs became more common in the workplace, there were already well-established Mac database products like FileMaker Pro, which Apple eventually acquired. Microsoft probably looked at the development cost versus the number of potential customers and decided it just was not worth the investment.
Some people also like to speculate that Microsoft intentionally kept Access as Windows-only to encourage businesses to stay on Windows. I have seen that argument many times over the years, but I personally do not think that was the primary reason. It may have been a nice side benefit for Microsoft, but I think the technical hurdles and the limited market were much bigger factors.
Looking forward to today, there is also the timing. As desktop databases start becoming less fashionable, Microsoft has shifted a lot of its investment toward cloud technologies. We have got Power Apps, Azure, Dataverse, and other web-based business applications. So instead of spending millions rebuilding a native Mac version of Access, they put those resources into cloud platforms that work everywhere.
They are still continuing development on Access for Windows. We have seen lots of new features in the last couple of months. We got Form Zooming, we got large form support, and we got all kinds of stuff coming out. But asking them to invest additional millions into making a Mac version probably is not a wise ask at this point.
If you are running Mac and need Access, there are still some good options. The one I hear recommended most often is Parallels Desktop, it lets you run Windows right alongside macOS. From everything I have heard from my moderators like Alex and some other students and my forums, it works extremely well with Access. You do need a Windows license and an Access license of course, but it is probably the smoothest experience.
You can also use VMware Fusion or any other virtualization software that lets you run Windows on your Mac. I am not a Mac person myself, I have not used an Apple product since high school in the 90s. This is just what I have learned from talking about it with my students and other Access experts over the years.
Another option is Remote Desktop. If you have got a Windows PC at the office that is running Access, or even a cloud-hosted Windows machine, you could simply remote into it from your Mac and run Access there. That is what I do when I am traveling or vacationing; I just leave my PC on at home and then I can remote into it. You can do the same thing from your Mac.
No, there is not a native Mac version of Microsoft Access and honestly, after all these years I would not expect one. There are still plenty of ways to run Access on a Mac today, but as far as getting an actual Mac version, probably not.
Next up, I got a lot of positive feedback on my recent Power Apps videos. If you have not seen them yet, I showed how you can take an Access database, move the data to SQL Server, and build a mobile friendly front end using Power Apps.
One comment and an email that I got comes from George Hepworth, a longtime Microsoft Access MVP. George has been building Power Apps for years and he reached out to wish me luck and pointed to his YouTube playlist. He has got a ton of videos on there with Access and Power Apps. I had no idea. Usually, I do a little research before I make a video of anything. I did not come across this at all. He has got tons of awesome videos. So check them out. I will put a link down below. There is a link right there you can use or you can click on the one in the description.
If you would like to take a deep dive into a lot of Power Apps with Microsoft Access, definitely check out his channel. I will probably do a couple more Power Apps videos in the future since you guys seem to be really interested in it, but nowhere near as many as he has got.
George also made a great point about licensing. The biggest hurdle for many people is not learning Power Apps. It is the cost. Once you start using the premium connectors like SQL Server, licensing can get expensive. It is important to understand those costs before you jump in. I might do a follow-up video showing some of the free connector options also.
George mentioned that another Access MVP, Carl Donabauer, has built Power Apps solutions for his clients using SharePoint lists instead of SQL Server, mainly because SharePoint is listed as one of those standard connectors, not a premium connector like SQL Server. So you do not get hit with that extra $20 a month premium Power Apps licensing fee. You do still need the appropriate Microsoft 365 and SharePoint licensing, but that's a lot easier for people to get started with without the extra SQL Server connector cost.
So thanks again George for the kind words and for sharing your experience and for putting together such a great resource for the Access community. So everyone else please check out his channel and watch some of those videos.
Sticking with the Power Apps stuff, by far the number one question I got after publishing that Power Apps video was, is Power Apps free? I keep wanting to make it one word but it is Power Apps. Let us fix that.
I thought I answered that clearly in the video but apparently I did not spend enough time on it. So let us clear it up because the answer is, it depends.
There really are three different ways you can use Power Apps. First, there is the Power Apps Developer Plan. This one is completely free but it is designed for learning, experimenting, and building apps while you are figuring things out. You can create apps, test them, connect to different data sources, and basically learn the platform without paying anything, but the catch is it is for development and testing only. Microsoft does not want you building production business applications on the free developer plan and then handing them out to your whole company.
Second, there are the Power Apps included with certain Microsoft 365 business subscriptions. If you already have something like Microsoft 365 Business Premium, E3, any of those, then you have already got access to build Power Apps that use what is called the standard connectors. Those are connectors that connect to things like SharePoint, Excel, OneDrive, Outlook, Microsoft Teams, and some other services. If you are already paying for one of those Microsoft 365 plans, you may not have to pay anything extra to build and run those kinds of apps.
Here is where the costs start. The third level is using the premium connectors. That is what I demonstrated in my video when I connected Power Apps directly to SQL Server. SQL Server is considered a premium connector. Once you start using the premium connectors, then you need Power Apps Premium licensing and that is where that additional $20 a month comes in. That is what George Hepworth was referring to when he emailed me.
If you are just learning Power Apps, it is free. If your company already has the right Microsoft 365 subscription and you are using standard connectors, then you may already have everything you need. But if you want to build Power Apps that connect directly to SQL Server, like I showed in my video, then yes, you will need premium licensing and that is where you will want to understand the cost before you build your application.
Microsoft licensing has never exactly been known for being simple. So hopefully that clears things up a little bit. I have to look all this stuff up myself too. They change it every couple of years. It is like Microsoft Office versions. There is all this, there is this, there is that. They need to simplify it.
One thing I do want to take a minute and tease is something I have been working on and off now for a couple of years, just in my spare time. It is an Access to web converter. Getting your data up in SQL Server on the web is pretty easy to do. I have got whole courses, including some free videos on how to do that. Once you get your tables connected, you can continue to use Access locally and then connect whatever other front end you want to your data, including Power Apps, including a web page if you want to take the time to build one.
What if we could take our Access forms and convert these over to a web page? That is what this does. This is my Access to web converter. It takes this form and turns it into a web page. If I want to open up, let us say, Jean Luc here in the database, I can come over here and open up Jean Luc on the website and it is the same data. It literally exports the form to look like the form in your database on the web.
I have got to add some custom controls on the bottom. These are both now linked to the same tables up on the server. If I change this to John, it updates to John here. If I come over here and refresh this, it is linked together. They are linked to the same table. This is a web interface and this is my Access database. So this is something that I built a proof of concept for and I just need to take some time and finish it.
If you are interested in something like this, let me know, post a comment down below. If enough people are interested, I will get off my butt and actually get this thing finished and deployable. I have not decided if I just want to make this a template that is available or if I want to actually do a full course into how everything works. Post a comment down below, let me know what you think and if you are interested or not. From the people that I have talked to, getting your data online is easy. The real barrier is, how do I work with it now?
If you could take your existing Access forms, or at least use the form designer in Access because you are familiar with it, set up a cell phone template for your customer form, publish it up to your website and there you go. Now people can log on with their cell phones in your web page. There is all kinds of stuff we could do with it. It is just a matter of how much time I want to devote to polishing it up and getting it ready for distribution.
Continuing on with the Power Apps questions, a few people asked if Power Apps can connect to MySQL. Yes, it absolutely can, but just like SQL Server, MySQL is supported through one of the premium connectors. It is definitely possible. The important thing to remember is it is not really about the database itself. Power Apps can connect to a lot of different data sources. What usually determines the cost is whether you are using a standard connector or a premium connector. MySQL falls into the premium category just like SQL Server.
A few people have posted comments saying something like mobile is the future, Access needs to catch up with native web and mobile. I agree. Mobile access is becoming more and more important. Microsoft tried this years ago with Access web apps back around 2013 or so. Unfortunately, that crashed and burned. It never really caught on and they eventually retired it, which fueled all kinds of Access is being retired stories and gossip and everybody was all panic.
They got rid of Access web apps, which were not very good to begin with, to be honest. Personally, I would love to see Microsoft make it easier to take an Access database and publish it to the web, just like I showed you with the tool that I am trying to build, or generate a basic mobile front end, but they do not seem to be heading in that direction. That is where tools like Power Apps come in, or other third-party solutions. It is up to you and me to build our own tools.
Access is fantastic if it stays in its lane for building Windows desktop database applications. I do not think there is a better development tool available for rapid application development. Moving your data into SQL Server is not hard. The real challenge is choosing the right front end for the platform that you want to support, whether that is web, phones, tablets, or something else. That is where the future is going to be.
Next up, Adrian, one of my members, is asking if it is possible to send each client a Google form with some of their information already filled in, let them update that information if necessary, and then answer additional questions that change depending on how they respond. He is talking about my surveys video that I did.
In this video, I show how to build a general survey that anyone can fill out and then import the responses into Access. Google Forms also supports pre-filled links where you can populate certain fields before you send the form. That is handy if you already know things like the customer's name, email address, account number, or whatever else you want them to verify instead of typing in from scratch. You can also build conditional sections into the form. If they answer yes to one question, you can send them to another question with follow-up questions. If they answer no, you can skip that entire section, which makes it possible to build some pretty sophisticated questionnaires.
In the extended cut, I also show how to automatically pull those responses back into Access, either through Excel or by downloading the CSV directly from Google Sheets. That said, if you are building a true client intake system, I probably would not use Google Forms. It is really designed for surveys and questionnaires, but not as a personalized client portal. If your data already lives in Access or better yet SQL Server, I would lean toward building a simple web front end, which is exactly what I showed in the Power Apps video. Your client logs in, sees their own information, updates what they need to update, fills out the intake questions, and everything writes back to the database. There is no importing a spreadsheet, no matching records, no duplicate responses to clean up.
If you do not want to go that far, another option is the old-fashioned approach: just data collection emails. Send each customer an email with their current information already filled in, they make whatever changes they need, send it back, and then you can import those changes into Access. That is actually probably a better fit if your goal is just updating existing customer records instead of collecting anonymous survey responses.
Yes, Google Forms can do a lot of what you are asking, but I would choose the right tool for the right job. For surveys, Google Forms is excellent. For personalized client intake and ongoing customer data, I would either use a real web front end or a web application connected to SQL Server, something along those lines. Or you could do it with an email if they can just fill between the lines.
Next up, this is a follow-up to something I said in last week's Quick Queries. Someone had asked how to block YouTube ads, and I explained that I was not going to help people bypass the ads completely. If you enjoy a creator's content, those ads are part of how we all get paid. If you do not want to see ads, then you could pay for YouTube Premium instead. That way the creators still get a share of the revenue.
Brian sent me an email. He just wanted to know if I click the skip ad button, do you still get paid? The short answer is sometimes. It depends on the type of ad. Some ads pay for just being shown and some only pay if you watch long enough and others pay if you actually click on them. Do not ever feel guilty about clicking the skip button. I do it too. If the ad is not interesting or relevant to you, then skip away.
What really helps content creators like me is watching my videos, clicking like, leaving comments, sharing them with friends, and subscribing if you have not already. Even just the free subscribe, not even saying you have to become a member. All of those things help the YouTube algorithm recommend my videos to more people, and that is worth a whole lot more to me over the long run than you sitting there watching an ad for toenail fungus cream that you do not need.
Brian also mentioned in a follow-up email that he usually watches my videos on my website, but he still hops over to YouTube once in a while just to hit the like button. I really appreciate that. Every like, every comment, every bit of engagement helps YouTube realize that people are still interested not only in my videos, but in Microsoft Access in general. That helps keep the Access community alive and visible. Thanks Brian. Thanks to all of you who take a second to click that like button. It really does help. If you have not hit the like button yet, hit the like button for me. If you are not subscribed, hit subscribe and post a comment down below. Just say hi. How are you doing? How has your day been? No one ever asks me. How is my day? Just kidding. Just kidding.
Next up, Stephen asks if there is a way to get the old standard colors palette back in Access. He noticed that Office 2019 has the classic color palette, but in Office 2021 and in MS 365, he only sees the newer theme colors and he is wondering if there is a setting to bring the old one back.
That is a good question, Stephen. Honestly, I do not know. I do not have an older version of Office installed anymore to compare them side by side. I know Microsoft has changed the color picker over the years. In the latest Microsoft 365 update, they actually changed it again. It looks like this now. So they have changed it recently. This thing's still the same though, but this is new.
I am going to put this one out to the community. If you are still running Office 2019 or 2021, and you have figured out a way to get the old standard colors palette back, or if you know whether Microsoft simply removed it all together, let us know down in the comments. I would be curious to see what everyone else has found.
Before we go, do not forget to stop by my website and check out what is new. I have got tons of new developer lessons I just released, of course, the new Power Apps videos, lots of good forum discussions and all kinds of other goodies waiting for you.
Someone commented last week that my homepage looks like it is straight out of the 1990s. To that, I say, thank you. Seriously though, that is what I am going for. I have always been a very function over form kind of guy. I am very utilitarian when it comes to my web design. I want you to be able to find what you are looking for in just a couple of clicks. There are new releases, popular courses are right there, the latest forum activity. I do not need giant full screen videos and animations flying all over the place for people to be able to just find beginner lessons. Look at Craigslist. Millions of people still use it every day because it works. I am not Nike. I am not Apple. I am not even like Airbnb. I am closer to like a Craigslist or Wikipedia or Stack Overflow. That is the look that I am going for.
If you have any comments or suggestions, I am always open to ideas. If you have suggestions that would genuinely make my site easier to use without turning it into one of those websites where you spend five minutes trying to figure out where the menu is, let me know. I am all ears. I kind of hate modern web design with pictures, animations, and other distractions. I just like this. This is what I want to say. This is what I grew up with, but I grew up in a day when we had BBSs. We did not even have the Internet, but this is what I like. This is how I built it. This is what I am going for.
Also, do not forget, check out the Captain's Log. Not a lot new since last week. I think I just posted one thing about the wide form support in the beta channel right now for Access. I have been busy. I have been recording videos all week. I have not had time to update the Captain's Log, but I am overdue for a good Captain's Log article, so check it out.
While you are at it, check out the merch store, where I have got tons of hats and t-shirts and mouse pads. I have got a book on Amazon you can check out. Stop by and post in my forums and just say hi if you want to, or post in the comments down below if you are watching on YouTube.
There you go. There is another Quick Queries in the books. Now you know why there is no Access for Mac version and tons of other stuff that I do not feel like recapping. Usually I go through a quick recap, but I am drained. It is a holiday weekend, too. I have a weekend of dealing with dogs that are extremely agitated when there are fireworks going around. I am looking forward to that tonight.
Aside from that, everyone, enjoy your weekend. I hope you learned something. Live long and prosper, my friends. I will see you next time.Quiz Q1. What is the main reason Microsoft Access has never had a native Mac version according to the video?
A. Access is built around Windows technologies that are not easily ported to Mac
B. Apple restricts database applications on macOS
C. Macs are not popular in business environments
D. Microsoft Access relies on Linux-based libraries
Q2. Which of the following technologies does Microsoft Access heavily rely on?
A. Jet and Ace database engine, COM automation, and ActiveX
B. MySQL and PHP integration
C. Mac-exclusive frameworks
D. Linux shell scripting
Q3. Why might Microsoft have decided not to invest in a native Mac version of Access, aside from technical limitations?
A. The target market for Access was primarily Windows business users and Mac alternatives were already available
B. Mac users protested Microsoft applications
C. Access can run natively on Linux instead
D. Microsoft lost the rights to develop Mac software
Q4. What cloud technologies has Microsoft prioritized over making Access available for Mac?
A. Power Apps, Azure, and Dataverse
B. Google Apps and FileMaker
C. iCloud and AppleScript
D. Dropbox and Slack
Q5. What is the most commonly recommended method for running Microsoft Access on a Mac as discussed in the video?
A. Using Parallels Desktop to run Windows alongside macOS
B. Installing Access directly on macOS
C. Running Access via Wine for Mac
D. Downloading a Mac-compatible Access installer from Microsoft
Q6. What is an alternative to virtualization for Mac users who need Access?
A. Using Remote Desktop to connect to a Windows PC running Access
B. Installing Access from the Mac App Store
C. Using Google Sheets as an Access replacement
D. Creating a dual-boot Mac with Linux
Q7. Why did Microsoft discontinue Access web apps?
A. They did not gain popularity and were eventually retired
B. They were too expensive to maintain
C. They required new hardware
D. They only worked with Android devices
Q8. What is a major licensing consideration when building Power Apps that connect to SQL Server?
A. Connections to SQL Server require Power Apps premium licensing, which can add additional costs
B. SQL Server connections are free for all Power Apps users
C. Connecting to SQL Server limits app performance
D. Power Apps standard connectors always include SQL Server
Q9. What is considered a standard connector in Power Apps that may be a more cost-effective option according to the video?
A. SharePoint
B. SQL Server
C. MySQL
D. Oracle
Q10. What does the Power Apps Developer Plan allow you to do?
A. Learn, experiment, and build apps for testing and development for free
B. Build unlimited production apps for free
C. Host applications on any device without limits
D. Distribute business apps to thousands of users free of charge
Q11. When using Google Forms as described in the video, what feature allows you to prefill user data?
A. Prefilled links
B. Macros
C. VBA scripts
D. Access web forms
Q12. According to the video, what is a better tool than Google Forms for a personalized client intake system if your data already lives in Access or SQL Server?
A. A true web front end or a Power Apps solution
B. Excel spreadsheets
C. Printed paper forms
D. Flash-based applications
Q13. What did the video mention as a major challenge when moving Access data to the web?
A. Choosing the right front end for the platform you want to support
B. Getting data out of Access is impossible
C. Only Microsoft can migrate data to the cloud
D. Access can only export to CSV
Q14. According to the video, what is the main strength of Microsoft Access in today's computing environment?
A. Building Windows desktop database applications rapidly
B. Developing cross-platform web apps easily
C. Powering iOS and Android apps directly
D. Hosting cloud-native APIs without code
Q15. How can users help support content creators on YouTube, as mentioned in the video?
A. Watching videos, clicking like, leaving comments, sharing, and subscribing
B. Only watching advertisements completely
C. Submitting bug reports to YouTube
D. Donating via PayPal only
Q16. What was the response given when asked about bringing back the old classic color palette in Access?
A. The presenter did not know and asked the community for input
B. There is a secret registry hack to bring it back
C. Microsoft promised to restore it in the next version
D. You can import palettes from Excel
Answers: 1-A; 2-A; 3-A; 4-A; 5-A; 6-A; 7-A; 8-A; 9-A; 10-A; 11-A; 12-A; 13-A; 14-A; 15-A; 16-A
DISCLAIMER: Quiz questions are AI generated. If you find any that are wrong, don't make sense, or aren't related to the video topic at hand, then please post a comment and let me know. Thanks.Summary In today's Quick Queries video from Access Learning Zone, I'm taking on a question that comes up frequently: why has Microsoft Access never been available as a native application for Mac? It's a long-standing issue in the Access community and something many Mac users run into, especially when Access is a requirement at work.
To start, Microsoft Access stands apart from other Office applications like Word, Excel, or PowerPoint. Access is a full-fledged database development platform. If you've worked with it, you know it involves tables, queries, forms, reports, VBA code, macros, and plenty of automation, all deeply interconnected. This is much more involved than editing a document or crunching numbers in a spreadsheet.
In my view, the primary obstacle has always been technical. Access was fundamentally engineered around the Windows environment. It depends on key technologies such as the Jet and Ace database engines, COM automation, ActiveX controls, deep VBA integration, Windows API calls, ODBC drivers, and several other Windows-specific systems. Recompiling Access for Mac isn't simply a matter of flipping a switch. Nearly the entire application would need to be rewritten from the ground up for macOS.
There is also a business side to this story. Access has always had its strongest customer base in the Windows business world. By the time Mac started gaining real traction in workplaces, there were already well-established database tools for Mac like FileMaker Pro, which Apple went on to acquire. When Microsoft looked at the cost of developing a Mac version versus the size of the potential Mac user base, it probably didn't make financial sense to pursue.
Some people speculate that Microsoft kept Access exclusive to Windows intentionally in hopes of encouraging businesses to stick with their platform. While that might have played a role, I think the big technical hurdles and the relatively small Mac business user market were far more significant reasons.
Another factor is how technology trends have shifted in recent years. As desktop databases started to fade in popularity, Microsoft began to direct more development resources toward cloud-based tools like Power Apps, Azure, and Dataverse. These platforms are accessible from any device, regardless of the operating system. Rather than commit the huge resources required to build a native Mac version of Access, Microsoft chose to invest in cloud solutions that offer broader compatibility.
Access is still getting updates on Windows, with new features like Form Zooming and support for large forms. But expecting Microsoft to build a native Mac version now probably isn't realistic.
So, what can Mac users do if they depend on Access? There are several ways to make it work. I hear Parallels Desktop recommended most often. It lets you run Windows alongside macOS, and according to feedback from my moderators and students, it works very well for Access. You will need valid Windows and Access licenses, but the experience is generally smooth.
Other virtualization options, like VMware Fusion, are also available. Any virtualization platform that lets you run Windows on your Mac could work for Access, but I should mention I am not a Mac user myself. This advice comes from my experience over the years helping students and consulting with other Access experts.
Remote Desktop is another path. If you have a Windows machine at work or one hosted in the cloud, you can connect to it from your Mac and work with Access that way. This is what I personally do when I'm on the road; I just remote into my main computer back home.
All in all, a native Access for Mac isn't likely to appear, but there are still robust ways to use Access from a Mac today.
I also want to mention the positive response I received regarding my recent Power Apps videos. I explained how to migrate an Access database to SQL Server and then build a mobile-friendly front end using Power Apps. Microsoft Access MVP George Hepworth reached out to me about his extensive playlist on using Power Apps with Access. I wasn't aware his channel had so many relevant resources, so if you're interested in exploring this topic further, definitely give his videos a look.
George also brought up an important licensing point. The major barrier for many trying to use Power Apps is not the technical learning curve, but the cost. Once you utilize premium connectors, like SQL Server, licensing becomes more expensive, so be sure to understand these costs upfront. George also mentioned Carl Donabauer, another Access MVP, who helps clients build Power Apps using SharePoint lists instead of SQL Server to avoid the premium connector fees. SharePoint is a standard connector, so often you can work within the licensing you already have from Microsoft 365 subscriptions.
Since so many people asked after the Power Apps video, let me clarify the licensing question. There are basically three ways to get and use Power Apps. The Power Apps Developer Plan is free and designed for learning, but it is not licensed for production use. If you have certain Microsoft 365 business subscriptions, you already have access to Power Apps with standard connectors like SharePoint, Excel, OneDrive, and others; so you might not need to pay anything beyond your existing licenses. The costs start if you need premium connectors, such as SQL Server or MySQL, and that's when Power Apps licensing adds about twenty dollars a month per user.
Power Apps can also connect to databases like MySQL, but just like SQL Server, that falls under the premium connector category, so additional licensing is needed.
Now, when it comes to taking Access forms and moving them to the web, this is something I've been working on as a side project: an Access-to-web converter. Moving your tables to SQL Server online is straightforward, but transferring the forms - that's the big challenge. My prototype exports an Access form as a web page that looks and behaves like your original form, with the same data and connectivity. Both the web interface and your Access database are linked to the same tables. If enough people are interested, I might develop this tool further, either as a template or as a full video course, explaining how it works. Let me know if that interests you, because getting data online isn't the biggest issue - it's giving users a familiar and practical way to interact with it that is the challenge.
Some viewers commented that Access needs to catch up with mobile and web functionality. I agree. Microsoft once tried this with Access Web Apps, but it wasn't a success and those features were discontinued, leading to mistaken rumors that Access itself was being retired. For now, the best tools for making Access data available on mobile or web are Power Apps and similar solutions. Building your own tools or using external solutions is often the way to go, since Access is a stellar platform for developing desktop database applications but has limited direct support for modern web and mobile workflows.
On a related note, I received a question about pre-filling Google Forms for clients and building conditional logic in surveys. Google Forms does allow for pre-filled field links and supports conditional sections. In one of my other videos, the extended cut covers how to automatically pull Google Forms responses into Access. However, for a proper client intake system, I would recommend a real web front end connected directly to your data source, instead of relying on Google Forms, which is more suited to surveys. If that's not feasible, you can always use data collection emails to gather updated information from customers for import into Access.
Switching topics, someone asked about the classic Office color palette in Access. It appears that Microsoft has changed the color picker with recent versions and updates to Microsoft 365. If anyone still using earlier versions like Office 2019 or 2021 has insight on whether the old palette can be restored, please share in the comments. I would be interested to hear what others have discovered.
A quick note on YouTube ads, since someone emailed me about what happens when you click the skip ad button. Sometimes creators get paid just for the ad showing, sometimes only if viewers watch for a minimum duration, and sometimes only after clicks. Don't worry about using the skip button if the ad isn't relevant. For creators like me, it's far more valuable for you to interact with the video content, like, comment, or subscribe, as that helps the YouTube algorithm recommend videos to more people.
Finally, if you haven't visited my website recently, check out the new Power Apps video tutorials, developer lessons, and our thriving forums. I go for a simple, functional web design so you can find what you want quickly, without excessive modern distractions. If you have ideas or feedback that would genuinely improve navigation or usability, I'm always happy to hear them.
You can find a complete video tutorial with step-by-step instructions on everything discussed here on my website at the link below. Live long and prosper, my friends.Topic List Why Microsoft Access is not available for Mac
Technical limitations of porting Access to Mac
Business reasons for Access remaining Windows-only
Comparison with other Office apps on Mac
Discussion of Mac database alternatives like FileMaker
How to run Access on Mac with Parallels Desktop
Using VMware Fusion to virtualize Windows for Access
Access via Remote Desktop from a Mac
Microsoft's shift from desktop databases to cloud tools
Current development and future of Access for Windows
Introduction to Power Apps for Access users
Migrating Access data to SQL Server
Building mobile front ends using Power Apps
Importance of Power Apps licensing and cost
Ways to use Power Apps for free or with a 365 subscription
Premium connectors and their effect on Power Apps costs
Connecting Power Apps to SQL Server vs SharePoint lists
Building Power Apps solutions using SharePoint lists
Developing an Access to web converter tool
Synchronizing Access forms with web forms
Power Apps ability to connect with MySQL and other databases
Discussion about Access web apps being discontinued
Choosing web and mobile front ends for SQL Server data
Options for client intake with Google Forms
Prefilled links and conditional sections in Google Forms
Integrating Google Forms responses with Access
Alternatives to Google Forms for client data collection
Discussion of YouTube ad revenue basics for creators
Accessing the classic color palette in newer Office versions
Soliciting community solutions for Office color picker changesArticle Many people wonder why Microsoft Access has never been released as a native application for Mac, even though Word, Excel, and PowerPoint have been available across both Windows and macOS for decades. The answer really comes down to a combination of technical and business factors.
Access is fundamentally different from other Office applications. While Word processes documents and Excel handles spreadsheets, Access is a complete database development platform. It brings together tables, queries, forms, reports, VBA code, macros, automation, and many other interconnected objects. These elements work together in ways that go far beyond what you see in typical Office products.
On the technical side, Access was built from the ground up to rely on Windows-specific technologies. It is tied closely to components like the Jet and Ace database engines, ActiveX, COM automation, the Windows API, ODBC drivers, and deep VBA integration. These frameworks were never available on Mac in the same way they were on Windows. Re-creating all that underlying functionality on macOS would require rewriting huge portions of Access from scratch, which is a much bigger undertaking than simply porting over Word or Excel.
From a business perspective, Access found the lion's share of its user base in business environments that already favored Windows. By the time the Mac became popular for business use, there were already established Mac database products, such as FileMaker Pro. Apple even acquired FileMaker to make it the main desktop database for Mac users. Microsoft likely weighed the significant cost of development against a relatively small potential market and decided it was not a worthwhile investment.
Some speculate that Microsoft intentionally kept Access Windows-only to keep businesses on the Windows platform. While this may have been a side benefit, the much bigger drivers were technical complexity and market size. These are what stopped Microsoft from releasing a native Mac version of Access.
Fast forward to today, desktop databases have become less central as cloud technologies have taken off. Microsoft has put significant investment into cloud-based solutions like Power Apps and Dataverse. These platforms are web-based and can be accessed from any device, including Macs, so Microsoft prefers to focus its resources there instead of building a new Access version for Mac.
Even though Access remains under active development for Windows, the business case for creating a Mac version has only gotten weaker. That is unlikely to change, so Mac users who need Access have to use alternative approaches to run it on their machines.
If you are on a Mac and need to use Access, the most popular solution is to use virtualization software such as Parallels Desktop. Parallels allows you to run Windows alongside macOS, which means you can install and use Access on your Mac almost as if it were a native application. You do need to have both Windows and Access licenses, but many users report that the experience is smooth and reliable.
Other virtualization options include VMware Fusion and similar products that let you run a Windows environment inside your Mac. Although the setup process can be a bit technical, these solutions handle Access well once up and running.
Another option for Mac users is to use Remote Desktop software. If you have a Windows computer at your office or even a cloud-based Windows virtual machine, you can connect to it remotely from your Mac. This allows you to use Access and other Windows-only software even when you are physically away from the Windows machine. Many people find this a simple and effective way to work with Access from a Mac.
For those who want to use Access but do not want to rely on Windows at all, Microsoft has been moving toward web-based alternatives. For example, you can migrate your data from Access to a SQL Server database and then use Power Apps to create a mobile-friendly or web-based front end. This is particularly useful for organizations that want to give users access to data on devices beyond traditional Windows computers.
It is important to be aware of licensing when considering cloud-based solutions like Power Apps. Microsoft offers several ways to use Power Apps. There is a developer plan that is free for experimentation and learning, but it is not intended for production work. If your organization already has a Microsoft 365 business subscription, you may be able to build apps using standard connectors, which include services like SharePoint, Excel, OneDrive, Outlook, and Teams, at no extra cost. However, if you want to connect Power Apps to databases like SQL Server or MySQL, you need premium licensing, which involves an additional monthly fee.
If you need more affordable Power Apps solutions, you can try using SharePoint lists as your data source. SharePoint is considered a standard connector, so you can often get started without the extra premium fee, although you will still need appropriate Microsoft 365 or SharePoint licensing. This makes it easier for organizations to experiment with app-building without incurring immediate extra costs for premium connectors.
Another area where Access users are looking to the future is in publishing databases to the web or making data available on mobile devices. Microsoft previously attempted this with a feature called Access web apps, but it did not find widespread use and has since been retired. Today, the most common approach is to move your tables to SQL Server and then create a custom front end, either in Power Apps or as a web application. Some third-party tools let you convert Access forms to web pages, allowing you to design the front end in Access and then publish it online. This approach is still a work in progress, and the feasibility depends on your technical resources and willingness to experiment. The core idea is that managing your data in Access locally is easy, but making it accessible online requires additional planning and the right tools for the job.
A common question about Power Apps is whether it is free. The answer depends on how you use it. Development and learning are free with the developer plan, and many Microsoft 365 subscriptions include access to basic app development using standard connectors, so you may not need to pay extra. Fees come into play when using premium connectors such as SQL Server or MySQL for your app data.
Another frequently asked question is about collecting client data or sending out forms. Google Forms offers a simple way to collect information and responses, including the ability to pre-fill certain fields and build dynamic forms where questions appear based on previous answers. However, for personalized client intake or ongoing customer updates, Google Forms is not ideal because it is designed more for surveys than for secure, individualized data entry. If your data is stored in Access or SQL Server, it may be easier to build a basic web front end or use Power Apps, allowing clients to log in, see their personal information, and make updates that tie directly into your database. If you prefer a simple approach, you can email clients pre-filled forms and ask them to update any relevant information and send it back. You can then import the changes into Access. This method is better suited for updating existing records without dealing with anonymous survey responses.
People working with modern Office applications sometimes notice that user interface features, such as the color picker, change over time. If you are missing an old color palette you used to rely on, it is not always possible to restore it in newer releases. Microsoft frequently updates and redesigns interface elements, so specific options come and go. If you do not see a way to bring back a specific color palette or other legacy features, checking with other users in online communities may help determine if a workaround exists. Sometimes, these changes are permanent.
When working with Access or any Office tools, choosing the right solution depends on your goals and your audience. Access remains a powerful tool for developing desktop database applications very quickly, especially for Windows. Making your application cross-platform or available on the web will require moving your data to a more flexible back end like SQL Server and then building a front end that matches your requirements, using tools like Power Apps, custom web development, or third-party form converters.
Lastly, supporting content creators and the broader technology community helps tools like Access continue to grow. If you find online tutorials helpful, simple actions like watching videos, liking and commenting, and sharing content all help maintain the visibility of these resources and keep the community active. Your engagement keeps educational materials available for everyone seeking to learn or solve their technical challenges.
If you are running Access on a Mac, you may feel left out, but there are reliable ways to work around the lack of a native version. Virtualization, Remote Desktop, and migration to web-based platforms all offer practical paths forward depending on your needs and technical comfort level. As technology continues to evolve, exploring these options will help ensure you can work productively regardless of operating system. |
