>>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
>
>You'll need to copy the PRG files, as well as any SCX/SCT (if the error is occurring in a screen), VCX/VCT (if the error is occurring in a class) and FRX/FRT (if error is in a report), and you probably also may need to make sure you compile the EXE and APP with debug info turned on in the project. ... and hope that the problem isn't a Heisenbug.
>
>of course, an obvious question needs to be asked -- does the customer already have VFP installed, or are you planning to install your copy of VFP onto their computer?
First, thank you. I don't need to install VFP on their computer. I just run VFP?.DLL and it opens IDE and allows me to run or open files.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham