Without having to trace through a number of procedures, WBTrace can provide a permanent record plus the values of selected variables within the procedures. You can view these conviently by scrolling and searching for specific entries using TraceViewer. OnChange, LostFocus, GotFocus, Resize, DragOver and many other events are often entered at unexpected times or worse, recursively. With WBTrace you can get an accurate picture of what is really happening. Not all errors show up during program testing.
Many errors are intermittent in nature, only showing up under certain circumstances.
Once you have identified a problem area in you program, you can insert detailed traces into the relevant functions. Once an the problem occurs you have the debug information available for analysis. Once trace statements have been coded in you program, tracing is automatic, saving you the hassle of continuously stepping through your application in debug mode. By placing a trace statement before and after executing a critical part of your code, you automatically captures valuable performance information. By leaving the low overhead trace statements in your program when executing on users machines, you can easily capture valuable information.