>>>>SET COVERAGE TO output.log
>>>>
>>>>Then use Martina Jindrova's CVP tool to load the .log file, then export with sources, and you'll see the full program trace log instruction by instruction. You'll be able to see the order of events, which code caused it to return without descending into all levels, etc.
>>>>
>>>>The most helpful tool I've found for finding issues in code.
>>>
>>>I admit that I have never used the SET COVERAGE TO and need to learn it. If you know where I can download Martina's CVP tool, please let me know.
>>>Thank you.
>>
>>http://gorila.netlab.cz/_vfp.html
>>
>>Coverage Profiler.
>
>Thank you.

SET COVERAGE TO can be confusing. So can Martina's tool. :-)

What I do is save to a log file, go into CVP and select File -> New, load that log file. It may ask for source code paths. After that, File -> Export -> As log (with sources).

I save that file as .log.prg and then load it in an editor or MODIFY COMMAND, and search for class names or variable names or events or functions, to try and hone in on the general area of source code. Then PgUp and PgDn and see what it shows happened.

It's the best tool I've found for tracking down the cause of unidentified errors. I owe Martina Jindrova 10s of hours of labor savings over the years. I regard her kindness in writing CVP and the other tools she's done most kindly. Such a beautiful heart to give to people like that... a recurrent theme in so many in the Fox communities.