>
>The funny thing is that as soon as I added the "SET COVERAGE TO >C:\CLOG.TXT" line at the start of the program and ran the prg, it ran >within a second or so, just like the VFP5 environment. Very strange, esp. >since the previous effect was repeatable. So, the cause is still a mystery.
>

I think VFP has an internal sensor that recognizes the coverage logging process. This, in turn, causes VFP to step up to the plate and get with the program so-to-speak.

It's sort of like an Admin proximity detector. We've all seen this. The program is acting up for a user and finally they break down and call for the system administrator to come check it out. As soon as the Administrator is there, everything works right.

I think there's a little Tron guy inside the machine toying with you. <g>

Guy