Make VBA UserForms available for MAC.
Sorry for my elementary English, I meant to say don't grieve not complain
As a peaceful person, I make it a policy not to (openly) attribute to malice that can be explained by mere stupidity and negligence, especially when addressing an entity I am somewhat dependent on. I occasionally had positive responses to bug reports I submitted, but mostly not.
I have access to a Windows system through a remote desktop connection, and at times had had a windows installation under Parallels. Dual boot is not an option since much of my main work is done with academic programs running under UNIX, which I mostly can run natively on my Mac without any hassle thanks to the efforts of the SBgrid consortium (https://sbgrid.org).
Why should I not complain when MS sells to Mac users a product that is flawed?
Good advice to use a disk partition to install Windows, but I would have to have Office for Windows that I don't have, moreover a slowdown of the computer would be unbearable.
Annemarie don't complain about some industrial policy choices of MS that are incomprehensible to us, the question to ask is: why?
Paraphrasing Dante: "Perdete ogni speranza voi che entrate?" (Lose all hope you who enter?).
I added the question mark
I won't directly accuse MS of intentionally introducing flaws in Office for Apple products, but they surely seem to be quite neglectful when it comes to their support for the MacOS version. Of course, historically the Mac was first: "Prior to packaging its various office-type Mac OS software applications into Office, Microsoft released Mac versions of Word 1.0 in 1984, the first year of the Macintosh computer; Excel 1.0 in 1985; and PowerPoint 1.0 in 1987. (https://en.wikipedia.org/wiki/Microsoft_Office). Nowadays, Office updates for Mac usually are released a year after the corresponding Windows versions are released. I started using vba as soon as it became available, to write macros that facilitate data visualisation of the results of the numerous bioinformatics programs that I have number crunching on either a large Linux cluster or, for smaller tasks, on six of the eight cores of my iMac (Excel does not make use of these). When MS announced that they would no longer support vba in Office2008 for Mac, I had to send out an urgent alert to all those using my macros: Do not update!!!. Apparently, a sufficient number of other Mac users had similar problems, relying on various add-ins and extensions that were no supported, so MS had to re-introduce VBA in Office 2011. But that they have released ever since is very buggy -Why is there a find/replace option in the menu of the vba editor, if it opens the correct dialog but does not do anything? If you leave the macro module of a user interface open when you save the workbook in windows, you can edit it on the mac, but you cannot switch between the graphical view and the macro view. Why does "Application.PathSeparator" return an obsolete value that no longer matches the one used in the path returned by "Application.ActiveWorkbook.Path"? At least they fixed the atrocious way they in the 2016 version placed the sandbox you needed to place programatically read and write files in a folder hidden deeply in the "system" folder, a hidden folder where you definitely do not want common users to start changing things around. And why, oh, why, do they have to associate any Xribbon customization to the individual workbook, when where is no equivalent to the "Custom UI Editor" for OSX. While I have altered the macros that up to Office 2004 added custom menus to the top of the screen (thanks, Ron de Bruin https://www.rondebruin.nl) to generate the xml code for the Xribbon and the callback routines, I still have to use Windows to attach the XML code to a template file, or to update the Xribbon for an existing file that is no longer in sync with the growing macro collection.
Yes NEED VBA - trying to take a class where VBA is necessary is a huge issue when on a Mac; however, the class did say we needed Windows 10. So my bad, but still, Microsoft, WHY??
Antonio almost had the right idea, but instead of putting another Mac version on his additional partition, why not make the partition a Windows partition and use something like Bootcamp? I would, but I don't have enough space on the Mac I have. Fortunately, I have access to a PC desktop part of the time in one of the buildings I work in.
I have never understood why Microsoft bothers to make their Office products for Macs when they truly are not 100% compatible. And it seems that they even make them user-UNfriendly for Macs. I thought it might be something to do with making Mac users want to switch to a PC, but would that benefit them? I don't know - I'm just rambling.
I don't understand your wonder.
Try to give me a solution that allows me to overcome the problem and I will be happy to say that you are right
Antonio, what on Earth are you Posting about?
How could a new partition with OS Sierra, on which Office 2011 H&S was installed, be helpful here?
"Unfortunately…" what but that you forgot to run your spell/grammar checkers?
I solved it like this:
new partition with OS Sierra on which I have installed Office 2011 H&S
Just purchased Office 2019 ( one time purchase). Cant use vba editor for user forms
I review my thoughts. My oversight, certainly the lack of development is to be blamed on MS and not Apple.
on the question of compatibility I answer that on the purchase card it is written:
1 Use 1PC / Mac
2 Classic Version
3 System requirements: Windows 10 o macOS
The reason for choosing not to make Userforms available in VBA is obscure to many.
Antonio, could you review your thoughts?
When you purchased the license and were told Office 2019 was compatible with both Windows 10 and Mac OS, what exactly did that say about the separate versions being compatible with each other?
That’s the problem!
When you’re “of the idea Apple deliberately omitted this development…” how could that be, please? In this case, Apple is merely a platform. Only Microsoft does any development; only MS could omit anything.
Those are choices of industrial policy and not technical and still the Question remains, why does MS not make VBA UserForms available for Mac users?
Yes, Microsoft like many publishers spends a lot of time analysing Users’ behaviour and still, the Question is why they choose not to dedicate development time to people who would jump at the chance to make more of their products.
At Microsoft they spend a lot of time understanding the behavior of the users of their applications and the good comments, it is clear that they do not have time to dedicate to those who complain about it .....
I thank those who have looked [Annemarie H.] for a possible answer, I remain of the idea that apple has deliberately omitted this development, these are choices of industrial policy and not technical, it may be right but the correct information is missing!
I agree but when I purchased the license I was told that office 2019 was compatible both on Windows 10 and on Mac OS this is confirmed on the purchase card where it reports, in bold, in the system requirements just the compatibility with both platforms.
The video you liked to shows how to create a Userform under Windows - this no longer works properly under EXCEL for Mac OSX
Sorry but I don't think so, I send url where i clearly see how there is the possibility to insert Userform in excel 2019: https://www.youtube.com/watch?v=OdN4Rk1jG_U
You can use existing Userforms on Mac - however, it is no longer possible to create and edit them on the Mac, which is rather annoying.
Unbelievable missing Userform in Excel 2019 HS on Mac.
I saw a Youtube video where they presented a job with Excel 2019 and there was the Userform so what happens at Microsoft?
Surprisingly there is no VBA UserForms on MAC. This is not helpful, especially when you are working sometimes on a Windows-Computer and then on a MAC. So I'm blocked to continue the work on my MAC and have to wait until I'll get access to the Windows-computer.
Please add VBA UserForms to MAC-Excel.
Thanks in advance. Would be a great help.
Dennis Swaney commented
VBA access to the Analysis Toolpak is essential for many professionals, and it is a fundamental flaw that this capability is absent on the Mac platform. Please resolve the issue.