Visual Basic Support in Mac 2016

Anonymous
2015-07-10T19:25:34+00:00

Hi

Am I missing something? I've been periodically using the Excel 2016 for Mac updates but quickly abandoned them because my sheets rely so heavily on VBA and support for that seemed to be missing. 

I've updatd to the production version today (15.2)...and it still seems to be the case? The Visual Basic editor is..ahem...extremely basic with no menus, right click functions or anything. No ability to insert new modules either. Shortcuts don't work (breakpoint, run etc). 

What's going on? Is this it? Please tell me there's some security setting i need to switch or something...please tell me there's basically no way to create macros enabled spreadsheets in Office for Mac 2016?

Thanks

Microsoft 365 and Office | Excel | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2017-11-22T18:12:09+00:00

Hi Roberto,

You're not missing anything. UserForm support is being built right now and should be available in a few weeks. I don't expect userform support to arrive during the holidays, but I hope we have it before spring.

Thanks Gordon for the answer. I will wait after the holidays the microsoft present for christmas. 

I take this opportunty to wish to everyone a my particolary Merry Christmas. 

Roberto

Was this answer helpful?

10+ people found this answer helpful.
0 comments No comments

66 additional answers

Sort by: Most helpful
  1. Anonymous
    2017-11-19T10:54:27+00:00

    Good news !!!

    Excel for Mac V15.40 has an improved VBA editor.

    Here what the what's new section says

    mproved Visual Basic Editor

    Create and edit macros in the Visual Basic Editor using IntelliSense, VBA menus and toolbars, debug tools, an object browser and more.

    Hope that helps

    Cheers

    JC

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Jim G 134.1K Reputation points MVP
    2015-09-29T16:39:22+00:00

    Sadly, LibreOffice has bone headed management, as well. Their implementation of VBA is even more crippled than the Microsoft Office for Mac version. LibreOffice refuses to support AutoOpen macros (for "security reasons"), which pretty much rules out most macros that are useful. VBA works only in Calc, which means that it can't do anything to automate mail merges or presentations and the like. I think the LibreOffice macro language is lame, too. Don't waste your time with it.

    Of all the various software products available for the Mac I think Microsoft Office 2011 is far and away the best one to have and use.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Jim G 134.1K Reputation points MVP
    2015-10-09T16:11:04+00:00

    Do you know where we could find a list of features (1) currently available in Office 2016 for Windows and (2) previously available in Office for Mac 2011 that aren't (yet) available in Office 2016 for Mac?  Those of us sitting on the bench could then wait until Office 2016 for Mac has achieved parity with its former counterpart before making the "upgrade".

    Cheers

    Microsoft Office is a huge thing. There are tens of thousands of features, large and small. I don't know of an inventory of all Office features. New features are added, existing features are fixed or changed, and features are lost with each new build of Office. These builds come out every few weeks in updates for the Mac and for the PC, so maintaining a list of features would be a gargantuan task.

    There is one person who has devoted his time for the past couple of years to document VBA differences and come up with work-arounds for VBA on the Mac vs the PC. His 2011 site is here:

    http://www.rondebruin.nl/mac.htm

    When you visit Ron's site click the Mac Tips and Articles tabs for lots of helpful information. Also check his Home page and check under What's New to see even more.

    The lack of menu, toolbar, QAT and Ribbon customization is expected to be remediated soon. At least that is what I gather from the hints Microsoft has been making about their plans for Office 2016 on the Mac. If you're planning to customize the Ribbon, I recommend learning about **RibbonX**. That's how I anticipate that User Interface (UI) customization will occur so that it matches Office for Windows. 

    As for feature parity, I am completely disheartened. Office 2016 has been out a couple months now and still every day I learn about yet another feature that is broken or missing. Today I learned that the new Waterfall charts in Excel 2016 for Windows don't even render in Excel on the Mac.

    Microsoft has poured resources into mobile devices at the expense of the desktop and it shows. The mobile apps are wonderful. The desktop app has been neglected and the gap between the Mac and Windows versions of Office has grown to be an enormous chasm. The 2016 VB Editor and Microsoft Query SQL editor are in your face failures. Conforming to Apple's "sandboxing" rules breaks so much stuff it's ridiculous. Microsoft has not given me any confidence they have the will or the ability to bridge the gap.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2015-07-12T17:52:28+00:00

    Thanks Jim and Phil - yes the VBA editor is in a (very) sorry state. On the one hand its tough to believe that MS could release something so non-functional (as compared to previous release)...and yet, given recent efforts, i somehow have no trouble believing it at all.

    It would be nice to get some official word from Microsoft about this. I do a lot of VBA on my Mac on my commute. Is MS really expecting me to keep two versions of office on, or switch between Windows and OSX whenever i want to do something like add a module!? The old version of the VBA Editor was also very horrible (and incredibly slow) but it was at least functional.

    So frustrating.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments