Bring back a fully functional VBE (Visual Basic Editor for VBA)
Please bring back the full editor capability of VBE to Mac Excel 2016, like we had in Mac Excel 2011. As it is, the "slimmed down" editing experience of VBA is more like a notepad experience than anything - making it basically impossible to
* edit VBA from scratch,
* get syntax highlighting
* see a watch window
(Note: this title and description updated by Dan [MS] on 10/19/2015)
Hi All – The Visual Basic Editor was greatly improved in an update several months ago. If you don’t have the latest version of Excel for Mac, please go to Help > Check for Updates and update to the latest version to check it out. Thanks for all your comments and support for this feature.
If you notice issues as you are using the latest VBE, please let us know by clicking the smiley-face feedback button near the top-right of the Excel window.
Steve K [MS Excel]
OMG people, Complaining in this thread gets people NO WHERE FAST (except to spam people who are following this thread with useless complaints). If your really upset, open an official ticket with Microsoft.
For any of you who think this should be completed in a few weeks/months, clearly has no idea how complicated it is to re-write this entire functionality from the ground up. However, if you did your research, you'd have heard about Microsoft converting their ENTIRE programming language to linux/osx compatible. Once that's complete, re-building VBA for OSX will be much faster, and not to mention work much more closely to Windows VBA (Other than a few graphics calls, it should be nearly identical). So, while the wait sucks, it might be better in the long run than it ever has been in the past. Things are changing in M$, and for the better. It just takes time.
Ripped off? It's worse than that. We've been Microshafted. Since I have parallels I bought another copy of excel to use on win 7. it is to cry. As Dan of MS/XL says, "It's a big project (hee, hee, hee) but we're working on it (ho ho ho)".
Comments I hear are that nothing is being done. I can't believe I paid for an upgrade to get a dummy down version. I still have to use excel 11 if I want anything done. Total rip off. We should get our money back
Oscar Abarca Pena commented
Any update on this... it has been wile since Dan's comment. I feel ripped off I paid for Excel2016 to find out this is not full version.
I am with you folks. This is quite amazing that MS actually did this on purpose knowing the functionality XL gives people. Actually, I am not all that surprised that MS did something this stupid. So many people depend on XL you would think that they would actually think before doing something like this. I hope they make this better "someday".
We want JUSTICE !!! Respect Mac Users please !
Ian Page commented
Now SIXTEEN MONTHS since Dan Battagin said they're working on it. The world will end before they deliver. Count me another appalled Excel 2016 user. Luckily I still have Excel 2011. In fact, I'm in the market for Excel 2011 installer codes so I can prevent my business collapsing. Without them, I can't sell my niche Excel product because 2016 has no custom toolbar option.
Mark Keimig commented
Any progress on this? Converting to mac and some very important xlsm sheets do not work. There are missing functions like LCase plus the IDE is poor. Using excel 15.30 from office 365.
VBA for the Windows Office apps can interact with the windows file system.
Will VBA for Mac have any capacity to select files on a Mac machine and have client /server app automation. Ie: Use Access to open and interact with an excel sheet... ?
VBEeditor VBA Do Does Not Work Exist in Excel 2016 at of 2017-02-13.
There. Once google logs that it should help poor fools like me spending hours at free tutorials, paid tutorials (Lynda.com), searching for some simple declaration as above and finding no information except RSN (real soon now). I'm long in the tooth and I can assure you microsoft has been poisoning other company's wells since DOS 3.0. I was a developer even then and speak from experience.
I agree. What's the deal? Why is Microsoft going backwards with Macs? I just paid to upgrade from Mac 11 to 16 and I wish I hadn't. I want my Excel 2011 back
Any news? I have end users using Office 365 on Mac. Excel is not fully compatible with previous version. I keep receiving feedback about strange behaviour and I can do nothing. I have no tools to debug or prepare workaround if I cannot catch the problems.
I walked right into this. MS Invited me to upgrade, I said yes, now I can't do anything useful in VBA. They say "Develop in Windows and debug in Mac" - I did that, but there seems to be no debugging capability!
I'd like to go back to 2011, but I can't see how! Microsoft seems to have utter contempt for their users.
very upset about how microsoft treats her customers. excel 2016 mac is useless without vba at the standard of the 2011 version
Fortun Francois commented
The January update delivered step by step debug. But no possibility to spy or just seeing the data of a variable
What a pity and poor tool.
Kevin McCarthy commented
I upgraded to Office 360 and it has completely crippled my macro editing in Excel. My productivity has plummeted as a result. Why the heck am I even paying for this? I'm going back to 2011 and I'll stay with it until you eventually cleverly engineer its obsolescence.
Tyler H commented
How is it coming, @Dan Battagin?
I will simply not upgrade from Excel 2016 for mac until the VBE is ready. very stupid idea to exclude it in the first place
Here is yet another Office (Excel) user waiting for the VBE MacEx11 -> MacEx16 port. Any new updates please.
I got mac while using windows during work.
hope it could be as much more similar as it can be for windows.
Thus I don't need to remember so many different ways when I using them.