Forum Discussion
Excel Macro Runs *PAINFULLY* Slow
Hershner04 You mention that you run W10 on a Mac. That means you are running a virtual machine, either via Bootcamp or Parallels. Correct? Did you look at memory allocation to the virtual Windows machine? Am not a VBA person myself and know little about coding, but am running W10 on an almost 10 years old Macbook Pro (via Parallels) with far inferior specs than yours and notice no severe performance issues when comparing to more modern PCs/Laptops. Just a thought.
I fully agree. The code is not the problem. I have code that I run 10 years ago on the Excel and hardware of the time. It executed in 20s. The same code on 2021 hardware and excel now takes 8 minutes to run.
This is a one sides Excel problem with their newer versions. I would really like to know why? The hardware is much better but the performance is 24 times worse...
- BeenCodingVBATooLongNov 05, 2021Copper ContributorI have the same issue. Simple code that is at least 15 years old.
It just started taking forever to run.
If I wasn't so completely trusting in the motives of the product managers, I might think it was to try to force us out of VBA like they tried to before.- px03afkNov 05, 2021Copper Contributor
I might agree that MS is trying to get us off VBA. After all VB6 hasn't been supported for many, many years despite that fact that there are massive parts of the world that still use it.
I am about to revert to Office 2007 as this excel problem is just one of the many things I don't like about Office 365.
- px03afkNov 06, 2021Copper ContributorJust to add to this issue, I have just run a macro which was taking around 1 second to populate each cell and suddenly it started working as it did with Excel 2007. That is overall excepting that every so often it would slow down for a cell or two and then pick up speed again.
So for anyone who has suggested that the problem is with the way the code is written I would suggest that this evidence suggests that the code is not at fault but something in the VBA handling and/or interaction with Windows 10 is causing the problem. If only we could persuade Microsoft that this is the case and get them to fix the underlying problem. Of course, as has been suggested, this may be a deliberate ply to get us to stop using VBA. If so, what are MS offering as an alternative.