There is a bug with an Office 2016 VBA engine which results in the VBA Mid function to work extremely slow. Like thousands times slower. A simple script which is supposed to run less than a second could execute (and freeze Excel since VBA is a single-thread environment running in the GUI thread) during 10-15 minutes.
I solved it by executing the following commands in the command prompt of my Windows machine where Excel macroses needs to run.
cd %programfiles%\Common Files\Microsoft Shared\ClickToRun
officec2rclient.exe /update user updatetoversion=16.0.9001.2138
Don't forget to switch off office updates :)
You can find available Office version releases here:
https://docs.microsoft.com/en-au/officeupdates/update-history-office365-proplus-by-date?redirectSourcePath=%252fen-us%252farticle%252fVersion-and-build-numbers-of-update-channel-releases-ae942449-1fca-4484-898b-a933ea23def7
For more information and detailed examples, please read this awesome article:
https://support.microsoft.com/en-au/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clic
I solved it by executing the following commands in the command prompt of my Windows machine where Excel macroses needs to run.
cd %programfiles%\Common Files\Microsoft Shared\ClickToRun
officec2rclient.exe /update user updatetoversion=16.0.9001.2138
Don't forget to switch off office updates :)
You can find available Office version releases here:
https://docs.microsoft.com/en-au/officeupdates/update-history-office365-proplus-by-date?redirectSourcePath=%252fen-us%252farticle%252fVersion-and-build-numbers-of-update-channel-releases-ae942449-1fca-4484-898b-a933ea23def7
For more information and detailed examples, please read this awesome article:
https://support.microsoft.com/en-au/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clic
Немає коментарів:
Дописати коментар