In that way, you can determine which portions of your code are taking the longest time to execute. At the beginning of a section of code you want to analyze, you call the first routine (which saves the start time) and then at the end of the section of code you call the second routine. Add a small routine that saves a time value and another routine that compares that saved value to the current time and displays the difference. A good place to start is to add some 'timer code' in your macro. Problems like this can be baffling, and they often take some heavy-duty analysis in order to figure out. Even though Fredric's workbook is large (46 MB), the time differential between the two methods of running is bothersome. When he runs the macro outright, it seems to take forever to run, often taking 20 minutes or more to execute. When he is running the macro in the VB Editor using F8 (stepping through the macro), it completes in just a few minutes.
Fredric wrote about a problem he was having with a macro.
