There is a gizmo in the debugger called 'coverage logging'. (From the debubber window click on the 'tools' menu) You set it up to save to a .txt file. The file will show you each line of code that was run, and how long it took to run it - thus enabling you to see where the hangup is. I usually import the .txt file into a table and then index it by the times. You have to actually run the app (or program or form) FROM the debugger to get it to work - and it will run even slower beause VFP has to write that text file too. Not the smoothest solution - but it can be helpful at times.....

>I am having problems with a VFP50 application.
>
>It will sometimes seems to habg-up the machine by taking forever (up to 5 mins) to get out of the application. The task manager even sees it as not responding.
>
>Obviously, some users believe what the task manager is saying and just end the task :(
>
>The machine operating system is NT Worksation 4.0.
>The server operating ystem us also NT 4.0.
>
>This is a critical accounting application that was converted from a
>FP2.5 for dos environment to VFP50.
>
>Anybody can help me ?
>
>Thanks
>
>Pascal