|
FastExcel Execution Tracing
Because VBA is an event-driven language it can be difficult to work out the path execution takes through your code.
If you need to trace the flow of execution through a sequence of procedure and event calls you can use FastExcel Trace Profiling.
First you need to Add Profiler Calls to the VBA code you want to trace (usually start by adding to all modules and procedures), in exactly the same the same way as for Profiling.
Start VBA Trace
.png)
The Trace report is appended to a .txt file in the same folder as the active workbook, rather than as a worksheet report. This ensures that as much of the trace as possible survives a crash.
Stop VBA Trace
.png)
Use Stop VBA Trace to ensure that all trace results are written to the file.
The Trace Report .txt File
.png)
The starting number and indentation show the start and end calling level for the procedure.
Uncaptured Exits in the Trace Report
If uncaptured exits have occurred the last trace line shown will be indented and its calling level will not be 1.
See Show Profiling Report – Uncaptured Exits for a more detailed explanation.
|
