I intend to write about the best practices in the coming weeks, but let us get back to the issue at hand.The quickest way to display messages while the code is running is to use the Statusbar property of the Application object.I admit that allowing Excel to update the screen each time your macro makes a change, helps during development, but it slows down the code a lot.
Screen Updating = False how do i differentiate that from Application.
Screen Updating = True Coz i could never really honestly see the difference Additionally, Workbook 1 where the code is written actually opens up another Work Book which stores the results.
However, the exact same file when run on other coworkers' machines is having issues where the "Application.screenupdating" is being set to true whenever the code switches worksheets or workbooks. Some versions of Excel might react differently to the Screen Updating code feature. So I'm trying to change the recordsources for the two subforms on Form1.
Screenupdating = TRUE End Sub Again, when running on some machines - no problem (screenupdating remains set to false at all times), but when run on another machines, it switches to true. I have seen many posts on various forums regarding similar issues, but nothing regarding screenupdating working on one machine but not another. "JLGWhiz" wrote: The best I can do is recommend that you purge your code of the Select method and use the direct address method as illustrated in the snippet I suggested.
Are you looking for the solution to your computer problem? This site is completely free -- paid for by advertisers and donations.