I sprinkled some splits around the code to see if there was one area causing the problem. There must be something else in 2013 that’s taking a disproportionately long time compared to 2010. Have you experienced performance problems with 2013? Certain vba macros / codes take a long time to run or execute the actions required. Sometimes, there could be one or more macros which cover multiple processes and this status bar will be useful to know at which process, the macro has reached.The status bar will show the message “Macro running” as the code is running, and once the code is done, it will show “Ready” which is one of the default Excel messages. Display Status Bar = True With Worksheets(“Sheet1”) lrow = . Option Explicit Sub macro1() Dim i As Long, lrow As Long Application. My code opens templates, unprotects them, writes stuff, combines them into a final report, and reprotects them.The first thing I did was get stingy about my protection.Its main purpose is to allow you to put one spreadsheet on one monitor and a different spreadsheet on another monitor. My problem with SDI is that I was still using Excel 2003 menus for five addins. It forced me to rewrite them using the Ribbon UI – not a bad thing, but my client probably wasn’t including that cost in the cost of upgrade.
Recently a client of mine upgraded to 2013 with, let’s say, disasterous consequences.If you have turned off screen updating using the line Application. Screen Updating = False at the beginning of your code, then if any user runs the code, they will not know what is going on and think that the computer system is not responding. First, there’s the Single Document Interface (SDI). If you have two linked documents open and you calculate, both documents go into the calculation tree.That’s where every document is in it’s own application container. So it’s not exactly separate application containers.