The point worth mentioning here is Coverage Profiler is effective in determining the bottlenecks in the program which is to say: "Lines of code which take PROPORTIONALLY more time than other lines, it was not meant to be exact since the loading of VFP enviornment and the coverage profiler app on top of it adds to the processing time as opposed to the user running just the exe, it's relative in other words. Had no problem using just Coverage profiler to detmine bottleecks when dealing with 1.5 million plus record tables.

Simple logging can give you probably more accurate reading as far as execution time but it gets to be cumbersome when working on big chunks of code and getting exact reading is not as useful since the loading on the Servers, network and WS can impact that.

Hope that clarifies my point.