I'm happy to announce the imminent return of the Visual Basic development editor to Office 2016 for Mac!
What’s new with Visual Basic?
Many of you have noticed the limited Visual Basic development environment that shipped with Office 2016 for Mac, and have asked for the full environment to make its way back to the Mac. Later this fall we
will indeed be releasing an update that includes the full editor, including multiple code windows, breakpoints, watches, the Object Browser, and more!
Here's a short YouTube video demonstrating the development environment (complete with a few visual bugs we haven't resolved yet!), to whet your appetite.
This feature is scheduled for public release sometime in fall 2017. The release will not yet include the Forms Designer, although we do intend to bring that functionality back to Office for Mac at a later date.
This feature will be available for Word, Excel and PowerPoint for Mac only; OneNote and Outlook for Mac are not adopting Visual Basic.
We'll be releasing the new IDE to the Insider Fast program in a few weeks, and you should definitely give it a whirl! Send us your feedback or comments by opening Word, Excel, or PowerPoint for Mac, and click Send a Smile
on top-right hand corner. You can also reply to this post, and the team will get back to you shortly.
This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
That is really good news. This was the only down side to my move from Windows to Mac when I retired. I have had to keep an old Windows laptop working just to maintain my existing Excel file / tools that occasionally require updating and that involves macro
My IMac 27" screen has just failed (luckily within a 3-year warranty so is currently being fixed) but this was enough for me to reconsider my move to MacOS and get a new Windows10 laptop so at least my Excel will be fully usable again.
I will wait a bit longer and keep my fingers crossed that a fully functioning VBA editor is on its way as generally I have been very happy with the move to a Mac and MacOS (although my wife has a new DellXPS Windows 10 laptop, and hardware and particularly
the new Windows have definitely brought things closer to the Apple experience).
The question I have is will Visual Basic in Excel for Mac for the full 100% as functional as in Windows (macros, connections with MSSQL, etc.), so that my developed tools in Windows Excel can finally be used by Mac users?
There was a problem when using ODBC as a data source for a PivotTable. This was fixed last December. This is something to test.
There is a known major blocking error. This code fails in the current crappy VBE:
.CommandText = stSQL1
Currently there is not a programmatic way to initiate a connection. It is unknown whether this blocking issue has been addressed in the new VBE. My hunch is that it has not. If you join Insider Fast and can test this scenario, please do and file reports
against it if it has not yet been fixed. However, if the connection exists, you should be able to program the resulting querytable using the reduced command set in Office for Mac:
I see lots of questions about object model parity between Mac and Windows versions of Office. The object model is completely independent from the IDE and thus is not part of this particular effort to revisit the IDE. The object model depends on having the
actual features supported in the app, whereas the IDE is a separate feature that allows you to browse, edit, and deploy code that uses the object model that currently exists (and may change over time) in the apps. For example, Mac Excel does not yet have OM
support for Pivot Charts because the app does not have an implementation of Pivot Charts to begin with, but if Mac Excel gains the Pivot Chart feature it should also gain Pivot Chart object model support.
Each app team is keenly aware of the feature differences between the Mac and Windows versions. There is a separate effort underway to greatly improve the code convergence between the Mac and Windows apps, and that will make it much easier to achieve feature
parity. Due to OS and platform differences, the apps will likely never have precisely matching features and abilities (such as the security restrictions of the Sandbox on the Mac that constrain feature behavior). Stay tuned for separate Insider discussions
on app feature and object model convergence!
On a side note, I will be offline for vacation for the next two weeks and will follow up on any IDE-specific questions when I return. To Jim's point above, Forms will continue to run as part of macros as we roll out the new IDE; it's just that the new IDE
will not yet support editing existing or creating new Forms when we first release it. We will add that support in the future.
When it comes to something like being unable to make a connection via VBA, it's hard for us on the outside to know whether that's an IDE problem or an Object Model problem.
Regarding making a data connection, clearly, a new connection can be made using the interface, so Connection is working as part of the application. The IDE understands, but can not execute, the correct syntax. The failure seems to be in the communication
between the IDE and the Object Model. Is the Object Model at fault or is it the IDE? Over here developer land, we can't know. All we can do is alert you to the error and hope that it gets resolved wherever it lies.
I am an unpaid volunteer and do not work for Microsoft. "Independent Advisors" work for contractors hired by Microsoft. "Microsoft Agents" work for Microsoft Support.