Code slower in Excel 2013?

[Jan Karel Pieterse]

It is:

Code: Select all

Application.EnableMacroAnimations = False

[Rudi]

Wouldn't that be covered by screenupdating?

Other options maybe??
-- Application.EnableLivePreview = False
-- Application.GenerateTableRefs = xlGenerateTableRefStruct

[Jan Karel Pieterse]

It should. The proof of the pudding...

[Rudi]

The proof of the pudding...

Something that Hans has been doing a lot of lately....

[Jan Karel Pieterse]

:LOL:

[ErikJan]

6.6 seconds Excel 2013 (32 bit) on Win7 64bit (see above)
5.5 seconds when events are off

I did the control panel "thing" but that didn't change anything

(I thought I'd revive this as I hoped by now a patch would have been available or something)

[Rudi]

I don't think any patch will help this. IMHO I think that the VBA engine is just too bloated; new objects, properties and methods added to the libraries over all the previous versions has resulted in a rather cumbersome mass (if that makes any sense?)

[ErikJan]

I probably would tend to believe you if the differences would not have been that large, but from Excel 2003 to 2007 to 2010 this was always really fast... I thought.
However I just tried it in a VM running WinXP (no network connections) with Office 2007 and I get 5.2 seconds... that's hardly slower than my Excel2013 (but it could be the VM of course)

[ErikJan]

4.7 seconds in Office 2016 (32 bit); running in Win10 64-bit... Regretfully this data point is worthless as I'm running on a new (much faster) PC now...

[Rudi]

So then we can safely advise others with slow code to upgrade to the latest version of the application and latest hardware to improve performance...
(I'd say that is great advice!!!)

[ErikJan]

Guess that's generally applicable ;-)