Microsoft Office 2011 Mac 64 bit upgrade

I understand everything you said in your post.  When I was notified in October 2017 that Office 2011 would no longer be supported, I acquired a copy of Office 2016.

I had created a complex application in Excel 2011 (lots of macros).  When I started it up in Excel 2016, It would not run properly.  At this point, I don't remember all the things that would not run, but do remember concluding that I could not afford the time or effort to modify the application.  It wasn't just a case of tweaking the code for Excel 2016.  Some commands I had used were no longer valid in 2016 and I would have had to redesign a lot of code.

I reverted back to Office 2011.

I knew that, at some point, Apple would no longer allow 32 bit code, and at that point I would have to do whatever was necessary to get my application to run in Excel 2016 (or maybe now Excel 2019).  

The best thing would be that I will start up my application and everything will work properly.  The worst thing would be that I will have to do a complete redesign of the application.  Having experienced Microsoft upgrades to their products many times in the past, I hope it will be the former, but I am quite confident I will have to do the latter.

Hi I'm running MacOS Mojave 10.14.4 and Microsoft Office is still working but I always got a lot of warnings.

Your license is good forever on your current hardware.

The real maximum is that your license expires when your hardware wears out or when you ditch your current operating system.

Mac OS Mojave is an upgrade from High Sierra, so apparently High Sierra was 32 bit

and Mojave is 64 bit.  I can check with Apple, but your message says that my version of Office should work forever.  Thanks for your help, but I'm not certain that is true.

Assuming Apple has not gotten rid of any APIs that Office 2011 uses (*), if MS wanted to make a 16-bit version of Office 2011, would it be as easy as turning the "Compile for 64-bit" in xCode (or maybe more likely Xamarin), and then letting it run for a few days recompiling a few million (ten million) lines of code?

(*) Or inexplicably changed the names of functions as they are wont to do: "Collection:get(withCondition: excludingCondition: number)" will become (ItemCollection:getItemsWithCondition(_ excluding: returnNumber:)", and other such "pronoun-changing nonsense" that drives everyone batty)

If so, it should cost them - I don't know - at most a MW or so of power to run the compilation server, whatever it would cost to do a cursory QA on the resulting binaries (do they open, do they work as expected to a basic level), and then on-going update server costs?

Then they sell it as a paid $9.98 upgrade, with some tight leagalese saying that MS is in no way responsible for anything.  Profit per unit, somewhere between $1-8.  Depending on how many Office 2011 users are out there who don't want to shell out - whatever

• for a new version, or don't want to be ensnared by the Office 365 SAAS.  Minus whatever the costs of the bare-bones-QA they did.

Would it be that simple?

Given that OSX Mojave *will* actually run (correctly) Office 2011 in it's current 32-bit state, albeit with the warning that 32-bit will be unsupported at some unspecified time in the future - I'd think it should.

Of course, such a "just-a-dumb-recompile" job might not get speed benefits that come from specific optimizations for 64-bit, and perhaps run a bit slower (because it wouldn't do things to take advantage of being able to store - I don't know - store really big floating point numbers in one register instead of 2.

Of course, if it has pieces of assembly in it written specifically for a 32-bit Intel architecture..  Then it becomes more difficult.

Would it be that simple?  Or is this just extraordinarily naive, thinking of a few-million line codebase as if it were just "Hello-World-times-a-billion"?