Using the Profiler. 
 What to do first.
──────────────────────────────────────────────────────────────────────────────

 Make sure that all of the CA-Clipper object modules that make up your
 program are compiled with the /b switch - otherwise the results are not
 going to be a true reflection on the speed of the program.

 Start up the program, but don't run it.

 Enable the Profiler by toggling the Profiling switch under the Profiler
 menu.

 Select the Disable All AltD()'s option from the Disable sub menu of the
 point menu. This allows your program to ignore any ALTD() functions embedded
 in your code.

 Run your program using the Fast Run option from the Run Menu. Run every
 single option that your program has, including reports, data entry, data
 collection, hidden screens, back doors etc, everything must be run so that
 the profiler can be recognize each and every part of the system.

 If you know how your program is going to be used, i.e. the data entry screen
 will be used constantly, whilst the monthly reports are run once per month,
 the yearly reports once per year, then try and simulate this - try and add
 real life usage to your running of the program whilst the profiler is taking
 it's timings.