>Doe's VFP have a profiler? That is, after our code is updated and complete,
>we'd like to find the critical sections of the code and see if we can speed
>the program up a bit.

Yes, you can turn coverage on with SET COVERAGE or through the Debugger. Then, run your app and do typical things (or whichever activities you want to profile). Once you've generated a coverage log, the Coverage Profiler tool can parse it and show you the results.

Do be forewarned that turning coverage off slows down the application.


OTOH, should we even bother with this, especially when
>we take into consideration that most of the things we're all doing with
>VFP are IO bound?
>

Good question. If the app runs satisfactorily, don't bother. If users are complaining or it seems slow, this is a good way to start tracking the problems down. As you dig into specific problems, if they involve SQL commands, take advantage of SYS(3054).

Also, keep in mind that what you may actually need to change is settings rather than code. For example, SYS(3050) controls the amount of memory VFP thinks it has. Finding the right setting for that is important because VFP is seriously into caching things. If it's paging because it doesn't has as much actual memory as it thinks it does, VFP can be very slow.

Tamar