Office 365 versus desktop Excel macros
Office 365 versus desktop Excel macros
Office 365 versus desktop Excel macros
Re: Office 365 versus desktop Excel macros
[...] we've been told that we're more definetely moving to the Online platform of Office 365, and as you already know, Excel online does not supports macros -or any VBA really
That is correct. VBA is a COM technology that has a lot of dependencies on Windows-specific things. That Microsoft managed to get it to run on Mac is rather impressive already, and I'm not even mentioning the fiendishly complex work of making a workable Mac-VBA editor.
VBA will be supported on Windows desktop for the foreseeable future, but making it work on all the platforms Office 365 runs on is simply unrealistic, and isn't going to happen.
Is that the death of VBA? Of course not. Microsoft knows there are millions of business-critical macro-enabled worksheets out there running VBA code, and as far as I know VBA will definitely keep being supported *on Windows*.
If your company is moving to Office 365 cloud, then your VBA code needs to be ported/rewritten in TypeScript, using [office-js](/questions/tagged/office-js), from scratch: that *should* have been a cost that was factored into the decision to go all-web. If your company isn't prepared to have all VBA code ported, then depending on how business-critical the VBA code is you'll want to keep a desktop install for the workstations that need to run VBA code.
The Microsoft Office Extensibility team is actively monitoring the [office-js](/questions/tagged/office-js) tag on SO, Michael being the top answerer in that tag.
You'll probably want to get into the insider program to benefit from the latest bug fixes and new features, as Office-JS is under very active development, and user feedback is absolutely welcome and taken into account.
Disclaimer: I'm a Microsoft Excel MVP.
That is correct. VBA is a COM technology that has a lot of dependencies on Windows-specific things. That Microsoft managed to get it to run on Mac is rather impressive already, and I'm not even mentioning the fiendishly complex work of making a workable Mac-VBA editor.
VBA will be supported on Windows desktop for the foreseeable future, but making it work on all the platforms Office 365 runs on is simply unrealistic, and isn't going to happen.
Is that the death of VBA? Of course not. Microsoft knows there are millions of business-critical macro-enabled worksheets out there running VBA code, and as far as I know VBA will definitely keep being supported *on Windows*.
If your company is moving to Office 365 cloud, then your VBA code needs to be ported/rewritten in TypeScript, using [office-js](/questions/tagged/office-js), from scratch: that *should* have been a cost that was factored into the decision to go all-web. If your company isn't prepared to have all VBA code ported, then depending on how business-critical the VBA code is you'll want to keep a desktop install for the workstations that need to run VBA code.
The Microsoft Office Extensibility team is actively monitoring the [office-js](/questions/tagged/office-js) tag on SO, Michael being the top answerer in that tag.
You'll probably want to get into the insider program to benefit from the latest bug fixes and new features, as Office-JS is under very active development, and user feedback is absolutely welcome and taken into account.
Disclaimer: I'm a Microsoft Excel MVP.