Syntax for 'Set Coverage' is in VFP Help. Philosophy behind this tool, as explained at Devcon '97 was to develop a code performance monitoring tool. In other words, the column with elapsed time spent on the line of code should be 0.000 for good efficient coding, and if you see something like 2.543 you know you have a "piggy" statement, which should be examined ( of course some statements like 'Index' or 'Pack' can legitimately take seconds, but most of the lines of procedural code that I see in the 'log' files have 0.000 time. Thus, the important thing for me is a detailed 'log' of all the procedural VFP statements that I ( or a member of our team ) has coded. Have had some real surprises that have helped me debug 'methods for events' that I didn't think should fire, or fire in the order that they did. CAVEAT: I do not suggest you run the entire application with 'SET COVERAGE...' since it does write a lot of records ( but is still a whale of a lot faster than DEBUG window with SET COVERAGE ). I think there is a file / FAQ or article in Foxpro Advisor ( somewhere ) where the author created a table and appended from the comma delimited file for programatic analysis -- he indexed on source module, statement number etc. Hope this helps.