
Originally Posted by
MarvinP
"One test is worth a thousand opinions".
Too True 

Originally Posted by
MarvinP
PLEASE let us know the results.....
See test code at the bottom of this post. (I decided to use 50,000 loops. 1000 wasn't enough to show up any real difference).
My results were:
method 1 = .172 seconds
method 2 = .109 seconds
method 3 = 8.219 seconds
Results will vary by computer performance of course.
My conclusion:- Method 1 is superior as it is fast & it is is the easiest to read
. - The speed difference between 1 & 2 really is negligible. (Remember I am talking about 50,000 loops here. If you set it to say 1000 then there is no recordable difference between 1 & 2)
- Method 3 is clearly the worst in terms of speed (And the result shown here is an optimal result - I tested it in an new XLSM. My theory is that the more macros you have in a project, the more procedures VBA will need to search in order to find the macro to run and the slower method 3 will become).
P.S. I remember now why I used to use Application.Run. Unlike Call, Application.Run has the ability to call a module level sub in a different module. (But then again - either make the sub you are calling project level or move the sub to where you really need it
)
Bookmarks