Help Needed with Screen Updating Code

I have written some code where it will turn on screen updating just long enough to input a text value into a cell that explains to the user what the current status is for the procedure. Once the status is inputted into the cell, I then the VBA turns off screen updating so that the rest of the procedure will run in the background. This is in order to help the code to run faster and to eliminate the screen from constantly flashing.

Next, once the code gets to a certain spot in the procedure, the code will turn screen updating back on, input another status value into the next cell to show the user the latest status of the current procedure. After that cell is updated, screen updating is turned off again while additional steps are completed in the background.

However, even though I am specifying code to turn on screen updating, enter the cell value with he status value and then turn off screen updating, I’m finding that the cells do not show the updated status value until after the entire code has finished running. Does anyone know why it doesn’t show the status as the cell value until the very end?

Is it a speed thing where screen updating is set back to true, but because the code is running so fast, it does not update the screen in time for the inputted value to be displayed in the cell before screen updating is set back to false? If so, how would you recommend fixing it? I want the status to update the cells o that it can be seen by the user the moment it is updated, not at the very end. Thanks in advance.

Not sure, but as a debugging method, you could try adding

Please Login or Register  to view this content.

right before the line that turns screen updating back off, to force a pause. That way you could see if the value is being shown while screen updating is on. you could drop another one in after the next time you turn screen updating back off, to see if the timing of the MsgBox forced pause makes a difference in whether or not the value update can "outrun" the screen updating changes, perhaps?

I'd ask if you could post a sample file, but I imagine without a substantially large data set, the full code would run too fast to see the issue you're experiencing...

Not sure if this will help, but it's what I would try first - try adding 'DoEvents' above the line where you turn screen updating back on.