AppleScript is old news, what you had to use in Excel 2008 from which Microsoft had removed VBA. In Excel 2011 for Mac, Microsoft has re-introduced VBA, and it's even finally the same version of VBA that Excel for Windows has been using all along. However, there are a substantial number of differences in how Excel itself behaves between the two platforms, and in how VBA interacts with these platforms. I've only done enough testing to know it's going to be a lot of work to make my stuff compatible.
Ron de Bruin has started documenting the differences between Mac and Windows Excel VBA in.
Aug 17, 2016 Greetings, all, and thanks in advance for your time. Have an Excel file developed in Windows 10, Excel 2016. Contains a macro which is triggered by the user clicking on a picture object, and another macro which is triggered as a 'change event' when user enters anything into a particular cell. Re: Change VBA code for Mac compatibility It's a read-only property in the replacement class. Remove that line I think since vbTextCompare (=1) is the default.
And give it a thumbs up. Big Update to the VB Editor for Mac I know many Mac users have been waiting along time for this, and I'm excited to share that an update to the VB Editor is finally here!
Microsoft just released a new build of Excel that contains a new VB Editor, which we use to write VBA macros in Excel. The new VB Editor contains a lot of the features we are used to seeing in the Windows versions of Excel, or Excel 2011 for Mac. In the video above I highlight some of the many new improvements to the editor. Here is a list of the major new features.
Vba Code Definitions
Intellisense drop-down menus for auto-filling code. Toolbars with buttons to for commands like: indenting, comment blocks, run, reset (stop), step into, etc. VBA Project, Properties, Immediate, Locals, and Watch windows. Debugging features and options. Keyboard shortcuts listed next to each command on the top menus. This new VB Editor feels a lot more like the VB Editor we are used to on the Windows version of Excel.
The one notable feature that is missing right now is userforms. The latest version (7.1) does not have any features that allow you to create, modify, or even view an existing userform. I'm hoping that will be updated in the near future as well. You can on the Excel UserVoice site. Microsoft uses this site to help prioritize feature updates, so please vote there if you want userforms back. Even with the absence of userforms, this new VB Editor is a huge leap forward from the editor that was originally shipped with Excel 2016 for Mac. If you are a Mac user, you will now be able to write macros to help you automate Excel and save time with your job.
If you are new to macros or want to learn more, checkout my upcoming. Get the Office Insiders Fast Pre-Release Build Important Note: You no longer need the Insiders Fast build to get the new VB Editor. You might just need to update Office which can be done from the Help Check for Updates menu. Here is the page with the that lists all the recent updates. To get the updated version you will need to be on an Office 365 subscription and on the Office Insiders Fast Program.
That program is free to join and open to everyone. It allows you to download and install pre-release builds of Excel. The latest build is 16.6 at the time of this writing, and it includes PivotCharts and a new VB Editor for writing VBA macros. Two awesome updates for Mac users.
It's really easy to do! Help Microsoft with Feedback As part of the Pre-release Program, Microsoft would love to get your feedback on how to make pivot charts better. If you find any bugs or have any suggestions you can provide feedback by:. Clicking the smiley face icon in the top-right corner of Excel. Click the “Tell Us What Can Be Better” option. Complete the form and hit Send.
The Excel development team will receive the feedback and use it to make Excel even better. If you are excited about this update, please leave a comment below and let us know. August 4, 2018 Yikes! And thanks Ian! 🙂 Just to clarify, I was referring to the VB Editor that was originally shipped with Excel 2016 for Mac.
It wasn’t much of an editor and looked like the following. No toolbars or debugging capabilities. This new editor is definitely a step forward, even with the absence of userforms. I realize that Excel 2011 for Mac did have userforms, so compared to that it is still lacking features. You can run userforms on the Excel 2016 for Mac. They will just have to be developed in either a Windows version or Excel 2011.
I realize this is frustrating if you are only using Macs. In the past I have used Parallels on a Mac to run Windows, and it worked great. This is another option if you want to get the best of both worlds. Yes, it will come at a price, and no, I don’t get paid by Microsoft.
I hope that helps. August 4, 2018 You can also vote for the userforms feature on the Excel UserVoice site. Here is a link to that page. I added a link in the article above as well.
Excel Vba For Mac Tutorial
Microsoft uses that site to help prioritize updates based on votes. I think it’s also important to note that Macs still only make up about 8%-10% of total market share for personal computers. And MS and Apple are still competitors. So those two factors will probably always give priority to Windows versions of Office. Don’t get me wrong. I love Apple products too.
Our house is full of them. We just can’t expect our sports car to be good at off roading 🙂. Mark - January 9, 2018 Hi Jon, Thanks for your video above. I’m contemplating moving from PC to Mac, and trying (without much success) to understand how complete the VBA implementation is in Mac Office 2016. I recently tested an xlsm file I wrote in PC Excel 2007 on a friend’s Mac Office 2016, and it choked on trying to create a Word file from within Excel. This uses the lines: Set objWord = CreateObject(“Word.Application”) Set objDoc = objWord.Documents.Add Is there a newer way to do this in the most recent Mac implementation? I read something about sandboxing on the Mac Office, which makes me think “no”.
Wondering in general how complete the port of Excel VBA was to the Mac version.