Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Oh ok since you can't any place to purchase it then I understand...wait what are these?

Disc Version

http://www.amazon.com/Office-Mac-Home-Business-2011/dp/B003YCOJAS

or

Key version + Direct Microsoft Download link

http://www.amazon.com/dp/B003YCOJA8..._m=ATVPDKIKX0DER&pf_rd_r=08SZ5AEFM5J7EG2M0Z7J

https://www7.downloadoffice2010.microsoft.com/macdl/registerkey.aspx?culture=en-US&ref=macdl

Hey the 2011 key version is even cheaper than the 2016 suite ;)
Well..how about that? amazon! neh...direct download gives me headache at times.
I'm sure people can go and buy from them! good job!
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Well..how about that? amazon! neh...direct download gives me headache at times.
I'm sure people can go and buy from them! good job!

Took me all of 2 minutes to track down and at Amazon of all places. Who would have thought to look there :rolleyes:

Perhaps you never had any intention of purchasing it eh?

Mehh your moral compass is yours, I have no place to judge you. I just wanted clear up that it is in fact readily available for purchase.
 
Stealing should have "no resort", not "last resort". Wrong is wrong no matter how much you try to justify it.

While I'm not advocating that piracy is right, it's not stealing by definition, and hence should not be called as such. Although in cases of discontinued software (like older OS X versions) I would argue that it's morally okay to pirate them since there is simply no way to obtain them legally anymore.
3428.jpg
 
Took me all of 2 minutes to track down and at Amazon of all places. Who would have thought to look there :rolleyes:

Perhaps you never had any intention of purchasing it eh?

Mehh your moral compass is yours, I have no place to judge you. I just wanted clear up that it is in fact readily available for purchase.
you sure did...indicate where to buy.
[doublepost=1462640559][/doublepost]
While I'm not advocating that piracy is right, it's not stealing by definition, and hence should not be called as such. Although in cases of discontinued software (like older OS X versions) I would argue that it's morally okay to pirate them since there is simply no way to obtain them legally anymore.
3428.jpg
You know if there was a classic game from the 80s and there was no remake of it....sure..why not.
 
I would argue that it's morally okay to pirate them since there is simply no way to obtain them legally anymore.
I have to disagree with you, and shown above, Office 2011 is available for purchase.

I do believe its stealing insofar is you're getting something for nothing, and that something was (and is) formally sold for a price. I think you can obfuscate the issue with the graphic but at the most fundamental level, you're getting something for nothing, and against the wishes of the people who created the program.

I've heard those arguments before and other logical gymnastics but from my perspective its fairly black and white.

I think this definition more or less hammers home my point
you're taking something you're not supposed.
Capto_Capture 2016-05-07_02-07-38_PM.png
 
Last edited:
I have to disagree with you, and shown above, Office 2011 is available for purchase.

I do believe its stealing insofar is you're getting something for nothing, and that something was (and is) formally sold for a price. I think you can obfuscate the issue with the graphic but at the most fundamental level, you're getting something for nothing, and against the wishes of the people who created the program.

I've heard those arguments before and other logical gymnastics but from my perspective its fairly black and white.

I think this definition more or less hammers home my point
you're taking something you're not supposed.
View attachment 630416

It doesn't. You aren't taking anything, you are copying. There is a clear difference between stealing a DVD box from a store and pirating one online. In the former you physically take something that doesn't belong to you, meaning that someone else can no longer buy it.

Again, I'm not advocating for piracy. All I'm asking is that people use the correct word because such word exists. You don't call an apple an orange even though they are both round fruits, do you?

http://www.merriam-webster.com/dictionary/piracy
 
I am a heavy user of Office - Outlook, Excel, PPT, and Word. I work at a company where where there are 10s of 1000s of Macs, with internal community support and IT support. The only time we are asked not to upgrade/update is when it is known (by internal testing) that it breaks something or has unwanted effects (like overloading servers). This is the case with new OSs. They ask that we don't load it until they've tested it out. Obviously for new versions of Office software we don't get access until the company OKs it and makes it available. All company Macs are less than 3 years old. I follow the internal community discussions pretty closely. I upgraded to 2016 about 5 months ago. My reaction? Meh. Something things got better, some things worse. But nothing major on either side. Things where less than perfect until a big update a month or so ago - 15.21. Now things are relatively stable, running on El Cap. Not everyone has updated to 2016 and El Cap. But when someone is having trouble (OS or Office) the official response when someone running a down-rev platform is: update OS/Office to the latest. This seems to solve the issue. Still, I would have to upgrade someday, so why not now. I certainly didn't buy another copy of 2011 for my personal Mac. I bought 2016.
 
I am a heavy user of Office - Outlook, Excel, PPT, and Word. I work at a company where where there are 10s of 1000s of Macs, with internal community support and IT support. The only time we are asked not to upgrade/update is when it is known (by internal testing) that it breaks something or has unwanted effects (like overloading servers). This is the case with new OSs. They ask that we don't load it until they've tested it out. Obviously for new versions of Office software we don't get access until the company OKs it and makes it available. All company Macs are less than 3 years old. I follow the internal community discussions pretty closely. I upgraded to 2016 about 5 months ago. My reaction? Meh. Something things got better, some things worse. But nothing major on either side. Things where less than perfect until a big update a month or so ago - 15.21. Now things are relatively stable, running on El Cap. Not everyone has updated to 2016 and El Cap. But when someone is having trouble (OS or Office) the official response when someone running a down-rev platform is: update OS/Office to the latest. This seems to solve the issue. Still, I would have to upgrade someday, so why not now. I certainly didn't buy another copy of 2011 for my personal Mac. I bought 2016.
Excellent advice. You seem like someone who might know the answer to the one I posed earlier, as where you work seems heavily reliant on more of the features that office has. So the bit I was wondering is if you've had any experience with VBA for excel on the Office 2016 Mac version? (either on EL Cap, or an any other OSX or Office for Mac version combination for that matter). If not, is there anyone at your workplace who might know the answer to this?

If so, can you tell me what your (or their) experience of VBA was like on that? (especially in relation to Excel, as that's where I use it most). Being able to do this on the Mac would solve alot of problems for me if I can find a working version combination of OSX and Office Mac that has all the features I need. But in relation to VBA for Excel, which is the most important feature for me, information on the the net on this seems surprisingly scarce, so I'm really hoping that someone out there has tried it in the real world who I can ask. So if you (or anyone you know) can shed any light on this, I would definitely be very grateful. Many thanks in advance.
 
Never used VBA, sorry!
No worries. Thanks for trying though.

I'd look for updated reviews on 2016, there's a good chance it has been significantly patched since release.
Thanks also for your comment. In the past when searching for this stuff, info in the internet about what the 2016 version would or wouldn't do (especially in regards to features that programmers like me would want) was pretty scarce, and for a while there it was looking for a long while that it was becoming a project that was dead in the water. However, after reading your post, I did another search this morning, and actually found a few things came up. So looks like it might not be so dead and abandoned after all. It seems that the Mac version does seem to be catching up, although some features it looks like they're not even going to try to implement still. However, for anyone else like me that would just like to see this work universally across all platforms, then I'll provide links below to the stuff I found today. Keeping vocal about it can only help, right?

Anyways, the first link I found shows that they've already released a "for dummies" series book for 2016 that covers this topic...
http://www.dummies.com/how-to/computers-software/ms-office/Excel/Excel-2016/Macros-Programming.html

Also, the official developers site has some info now on what's supported, and some better comparison tables as to what the Mac version will be covering. http://www.dummies.com/how-to/computers-software/ms-office/Excel/Excel-2016/Macros-Programming.html (Seems better than on previous versions, but we still probably wanna push Microsoft to stop being so lazy, and just support all the features on the Mac version aswell.) Admittedly, I get that part of the problem is that running on different platforms has natural limitations due to the native libraries that it will be calling.) However, one other cool bit I learnt from that site is that the Mac version of Excel for Mac will start supporting AppleScript calls from VBA modules (so that might help bridge the gap in providing some kind of workaround for the natural limitations of not being able to call the COM libraries of windows). Will mean all sorts of messy "if statements" to get around what happens when a user transfers a spreadsheet between a PC and Mac, but at least it's now providing some capabilities. (I still think that it could be made more seamless by having some kind of common language runtime layer that acts as like a built in gateway interface between front end VBA code and the back end COM/Apple libraries that it calls, as that would have been a much tidier and seamless solution) but still, what I've seen today seems to be progress, so I'm going to try to encourage rather than just whine about it. So for the most part, this is good, and definitely a step in the right direction.
 
I'm looking for a one time purchase option. I mainly use excel.

What is the difference between 2011 & 365?

Office 365 is a subscription with automatic version upgrades and online storage. 2011 is a one time purchase with no upgrades to new versions (such as 2016) and no online storage included.
 
If so, can you tell me what your (or their) experience of VBA was like on that? (especially in relation to Excel, as that's where I use it most).

Second hand information, I'm afraid. From what I read on our internal community, not as good as it could be/once was. The people I work with who rely on Excel for their day-to-day tell me that's why they have a Lenovo, even if they have a Mac at home. For occasional use I use Mac Excel, but when I need to work on, or look at something that's a big/complex spreadsheet, I fire up Win 7 on Fusion. Much better Excel experience. But I realize that is not practical for most people - 2 OSs, 2 versions of Office.
 
Second hand information, I'm afraid. From what I read on our internal community, not as good as it could be/once was. The people I work with who rely on Excel for their day-to-day tell me that's why they have a Lenovo, even if they have a Mac at home. For occasional use I use Mac Excel, but when I need to work on, or look at something that's a big/complex spreadsheet, I fire up Win 7 on Fusion. Much better Excel experience. But I realize that is not practical for most people - 2 OSs, 2 versions of Office.
Thanks. (Sorry, I hadn't checked my MacRumors account in a while, so only just saw this).
But totally agree with you, Have since upgraded my Mac to Sierra OS, and bought an annual 3-computer license for excel, so was able to install it on both my windows and my mac. Regular spreadsheet stuff does work well on both, but you're right that the VBA experience is definitely still playing catch-up on Mac. (Also for proprietary code that I had written, had to build in code to recognize the different folder path structure, etc, when calling certain files). Was hoping that office 365 on OneDrive would be a good way around that when using it on the Mac, but it turns out that it's actually the client side office app that office 365 installs on the pc itself which handles all the VBA, so didn't really work very well that way. You totally do notice how far behind its VBA support is when doing anything advanced with it.
 
I have a MacBook 12" running Office 2016 for Mac and have no problems. I should mention I keep the OS and Office up-to-date. I'm also running Office 2016 on a mid-iMac 2011 and it works well. Part of the key to performance is Memory consumption. If you're running 8GBs, don't have a lot of apps open unless they're needed as it will slow down performance.
 
Office 2011 for retina MBP is OK. The downside is the hyperlink - took couple of seconds to launch the browser.

Office 2015 isn't bad. It's a bit bloated but it's much improved especially the hyperlink.

I prefer Google Doc or Rich Text Editor for quick editing :)
 
I have a MacBook 12" running Office 2016 for Mac and have no problems. I should mention I keep the OS and Office up-to-date. I'm also running Office 2016 on a mid-iMac 2011 and it works well. Part of the key to performance is Memory consumption. If you're running 8GBs, don't have a lot of apps open unless they're needed as it will slow down performance.

Yeah, definitely memory can be an issue in that respect. Fortunately I have plenty of memory on mine, so don't really suffer from that personally. So is just the VBA that is lacking a bit that's currently preventing me for using it fo the stuff I do. But it's getting better bit by bit though as more updates become available. So hopefully we'll get to the point sometime in the future where I can use my VBA coded excel files no matter which machine I happen to be accessing them from. (I think we're still quite a way from that yet though)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.