Hi everyone!
I've migrated to Excel 2013, and noticed that strangely all code runs waaaay slower. Not only that, but also the screen goes completely white while code is running- WEIRD.
I was using 2010 before and it worked just fine, never had this issue. Actually not even when I was running 2007. It happens with basic code too, nothing too complex.
Doing some research (yes, I saw the bit about disabling graphics acceleration, looks like that's not it) I found that due to a stronger algorithm, 2013 takes more time when protecting and unprotecting sheets. According to articles, it's a design flaw, so no workaround. Removed that and it's faster, but I still get the white screen while code runs.
Protecting via code is essential for my reports and dashboards, I know you can probably relate- not only does it make it more professional but it also protects the user from changing things around and affecting the report.
Has anyone faced this already? Any solutions to the protecting-via-code part, or reasons why all that white screen time happens? I find it really hard to believe that the new version is really this bad, especially with Excel that absolutely rules.
THANK YOU!
POST MOVED BY MODERATOR
.
I've migrated to Excel 2013, and noticed that strangely all code runs waaaay slower. Not only that, but also the screen goes completely white while code is running- WEIRD.
I was using 2010 before and it worked just fine, never had this issue. Actually not even when I was running 2007. It happens with basic code too, nothing too complex.
Doing some research (yes, I saw the bit about disabling graphics acceleration, looks like that's not it) I found that due to a stronger algorithm, 2013 takes more time when protecting and unprotecting sheets. According to articles, it's a design flaw, so no workaround. Removed that and it's faster, but I still get the white screen while code runs.
Protecting via code is essential for my reports and dashboards, I know you can probably relate- not only does it make it more professional but it also protects the user from changing things around and affecting the report.
Has anyone faced this already? Any solutions to the protecting-via-code part, or reasons why all that white screen time happens? I find it really hard to believe that the new version is really this bad, especially with Excel that absolutely rules.
THANK YOU!
POST MOVED BY MODERATOR
.
Last edited by a moderator: