>It's fine to track bottlenecks, but it ain't secure enough. The time that is covered in the log is incorrect. It gives an indication of the time needed to execute it, but it certainly gives the right time, especially for program lines that are really fast.
>
>For example run this program:
>

>x=seconds()
>
>nY=1
>FOR nt= 1 TO 1000000
>	nY=nY+nt
>ENDFOR
>wait window STR(Seconds()-x,5,3)
>
>m.x=seconds()
>
>m.nY=1
>FOR nt= 1 TO 1000000
>	nY=nY+nt
>ENDFOR
>wait window STR(Seconds()-x,5,3)
>

I don't doubt you Walter, but that's usually not the kind of bottleneck we're trying to find :) Also, like the debugger, duplicate event calls will show up in the Log, that's another benefit I've found several times.

Using The Coverage Log with

1) Markus Egger's Maxcov add-on
2) Dumping the log into a table and indexing on time Descending

will often give some very useful insights into virtually any vfp application.