The Profiler
 About the Profiler.
──────────────────────────────────────────────────────────────────────────────

 With the use of a profiler, you are able to see the approximate times that
 CA-Clipper Function and Procedures take to run.

 The profiler only works on those .PRGs that have been compiled with the
 debugging info switch /b.

 All information stored by the profiler can be displayed within the profiler
 window - this can be accessed with <Shift><Alt><V>, to open the profiler
 window and, if it is not already the current window, <Alt><9>

 The profiler is very memory intensive and very slow. It is recommended that
 you toggle the Fast Run option to on when you run the profiler and simply
 Run the program, running as many of your functions and procedures as
 possible.

 In this way, the Profiler can take speed readings of all of your functions
 and procedures for the profiler window.

 Please Note: You should only use the profiler, once you have finished
              tinkering with the source code. Should you change the source
              code whilst profiling, then the results gained may be
              uncertain.

              If you change source code, then you should start profiling
              afresh.



















































                       My reality check just bounced.