You could image the time consumption that might take place if you are running VBA code that is deleting or adding thousands of rows to a spreadsheet. One bad thing about page breaks when you have VBA code running is they want to recalculate the "breaks" whenever a change is made to the spreadsheet. I have a personal hatred for the visualization of page breaks, but I suppose there are a few of you out there who might like them. The only scenario I can think of where you might want it on is if your code is displaying some sort of animation on screen. 99.9% of the time, you will ALWAYS want to turn OFF Screen Updating. I would always say she was trying to brainwash me through the macro because there was non-stop screen-flickering for 30 straight minutes! Little did I know that a single line of code would have saved my eyes (and mind) from deterioration and at the same time speed up the code's runtime dramatically. The first macro I ever ran was a co-worker's that took 30 minutes to finish executing (it did a lot of stuff and was very poorly written). Let's look at these settings in detail to appease those of you who want to know why this code works. Your computer is simply trying to do too many things at once.
This slows your computer's processing power down and in turn decreases your computer's ability to run your code as fast as it can.
The above VBA code I just shared with you is simply turning off settings from within your Office application that want to use your computer's memory to report out on your computer screen every single thing your macro is doing (in real-time).
0 kommentar(er)
