Why Does Excel 2013 macros will sometimes notice "Not Responding" and shortly after the program goes forward.
Why Does Excel 2013 macros will sometimes notice "Not Responding" and shortly after the program goes forward.
Probably because it's busy running code, especially if you're running in a loop and updating a worksheet that causes cascading events.
Impossible to say exactly without seeing your code, but you could try adding astatement in a strategic point on the code; however, this will slow down the processing...![]()
DoEvents
Using the following code, the message "Not Responding" did not come (it code neutralizes the "Not Responding" message):
CreateObject("WScript.Shell").Popup "Found the answer to the following ...", 1, " Message ... "
Perhaps the VBA language finds that the program leads to a cycle in my code?
Excel 2007 environment, this message (Not Responding) does not appear, even though the macro code is the same.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks