Bruce,

>Use the Coverage Log! It is perfect for identifying bottlenecks, but hardly anyone ever thinks to use it. It will give run-time for all events & lines of code within, then just look at the large times to see what's slow. Note that the application will run slowly with the log on, that's normal, do not be concerned about it, it takes extra time to log in the code timings...

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)

If you cover the program, you'll see some time data that doesn't match the output from the wait window statements.

Walter,