>Neil
>actually i ran coverage too and it returns a no of programs in its list going thru each one of those programs can be nightmare.hope there is better way doing things !
>since i did not work coverage programs before probably am just wondering if there is any way of comparing to 2 coverage logs (one created with vfp8 app and the other one is vfp9 app).

The source code for coverage analyzer (or whatever the app is called) is included in the xsource.zip - check your VFP installation disk. You can add a button somewhere to save the current cursor into a temp table. Do that with both and simply compare the tables.

Hey, didn't say it was easy :).

My advice on using the profiler is to start and stop logging at places you know are slow - if it's a particular form, turn it on in .load and off in .destroy; if it's a reaction to a button.click, turn it on before the code called by .click and off after. You don't want to track the menu system etc - narrow it down in advance.

Then, just look at the top level code, and see which call took the longest. Or which was called more times than you expected. I've caught numerous unnecessary refreshes this way. Then look into the offender's code - which part of it was taking so long. Expect surprises and avoid having heavy objects in your hand while doing that, or slapping the forehead may hurt. Almost happened to me a couple of times :).