Hello, Tamar, and thanks for the reply. (Also, thanks go out to Hugo, Naomi, and
Borislav. This message is verbose, so I'll just reply to everyone here. :^) )


>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.

Kewl. Excellent.

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

I'm sure you meant that "turning coverage on slows down the app."
I do stuff like this, too. Just thought it was me :^). I sometimes
wonder if there is such a thing as verbal dislexia or something.

>>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.

Same thing that I was thinking. Not only that, but if things are slowing down
because of thrashing or queries and the like, we can prove to the
admins that the problem isn't in the client code but on the server.
And when that happens, we could all ask our admins/clients to purchase
an IBM blade server to play around with :^).


>As you dig into specific problems, if they involve SQL commands, take advantage of >SYS(3054).

Okay. I'll look into this tomorrow morning. Almost 5:00 P.M. here.


>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.

From my experience, _ALL_ Microsoft products are seriously into caching things,
especially XP. Hmmm. Now I'm starting to wonder how much mem I'll need for
Vista just to get things working and not constantly paging :^). Seriously,
you have to wonder if Gates has a standing order in the OS dev department
that states: "_ALL_ MS products _MUST_ 'seem' fast to our clients. If the
memory is out there, then grab it!" :^)


>If it's paging because it doesn't has as much actual memory as it thinks it does,
>VFP can be very slow.

This is great info, Tamar.

Thanks a bunch, folks. Hopefully, in the "not too distant future," Sameer
and I will be returning the favor. Again, thanks!

Randall