For instance, the Edit menu features some new options for viewing properties, methods, constants and parameters. The Visual Basic Editor’s work area is mostly identical to that of Excel 2004’s, but with a few nice additions. New macros I’ve recorded so far all worked as expected.

I also opened a number of Excel 2004 worksheets, all of which used macros to some degree or another, and they also worked as expected. I opened one macro-laden worksheet I’d created back in 1992 in Excel 2011 it ran perfectly. In my testing so far, Excel 2011 runs older macros just fine. Now, with the release of Excel 2011 ( ), Microsoft has brought VBA support back to Excel for the Mac-and the Tools -> Macro menu item is once again useful. You couldn’t, for example, use AppleScript to change Excel’s menu structure, to manage a data-input form, or to change spreadsheet values on the fly-all things you could easily do with VBA. But AppleScript couldn’t really replace the functionality of VBA. And if the sheet you were looking at included VBA macros, they wouldn’t run.Įxcel 2008’s macro window: sadly, empty.“But what about AppleScript,” you ask? Sure, Excel 2008 supported OS X’s built-in scripting language. But it wouldn’t show you anything written with VBA. Sure, that menu might show you some really old macros, the ones written in the Excel 4.0 macro language. It seemed to exist for no other reason than to annoy those of us who used and relied on Visual Basic for Applications (VBA) macros.

This time it’ll work-really, it will.”īut selecting Tools -> Macros in Excel 2008 ( ) would only remind me, once again, that the Macros menu was but a mere shell of its former Excel 2004 self. “Go ahead,” it would whisper, “You know you want to.

For years, Excel 2008 has been teasing me: Every time I launched the app, I’d see that menu item, mocking me, tempting me to click.

Visual basic for mac excel 2011