>>Hi,
>>
>>I am trying to duplicate the problem that a customer has, stepping through the debugger. What I plan to do is add SET STEP ON in the procedure where I need to start the debugger. Then build the .EXE (e.g. MyApp.EXE), copy it to the customer server. Then on the customer server open VFP IDE and call DO MyApp.exe. Do I need to copy all .PRG files where the debugger will step through? I should I compile these .PRG and copy .FXP files?
>>
>>TIA
>
>As Dragan points out, you run the exe from the IDE. All you need to do on a machine where the IDE is not installed is drop vfp9.exe where the dll's are installed (common files, etc.).
>
>Unless you removed code from the classes or forms, the code is already there. You will need the same version prg as the prg used to compile the program to observe it. Although without the prg there, you can still get the value of the memory variables.

Above all true (unless compiled without debug info enabled), but on deployment machines you can get bitten by vfp eagerness to help you: the first prg found according to machine layout, set path and so on will be loaded. Be careful to provide the correct üath to those prgs, esp. if other prgs are on the machine