title: Difference between Calling a Sub and Application.Run
body: <p>In my business, we have a few teams that work on very simple macros. I'm trying to make them all readable to each other and in somewhat of a similar format, so new joiners can start working on the data.</p>
  
  <p>I mention simple macros, because no one will be using Subs with arguments - most are derived from Macro Recorder anyway</p>
  
  <p>Half of the teams use:</p>
  
  <pre><code>Sub button()
  
  Call sub1()
  Call sub2()
  Call sub3()
  Call sub4()
  
  End Sub
  </code></pre>
  
  <p>And the other half use </p>
  
  <pre><code>Sub button()
  
  Application.Run("sub1")
  Application.Run("sub2")    
  Application.Run("sub3")    
  Application.Run("sub4")
  
  End Sub
  </code></pre>
  
  <p>I understand that if your sub has no arguments, then Application.Run has a use - but being as there's barely any notation on it - is there a reason people still use <code>Application.Run("")</code>?</p>
  
  <p>Can every use of it be beaten in speed and process by <code>Call</code>?</p>