David,

Correct that the debugger doesn't trace throught reports.

Usually the bad control will pop up after you close the error box. It may be in the expression itself, in the 'print when', etc. It could also be in the grouping or the report variables. It's probably a typo of some sort.

Another way to look through systematically is to USE the frx and open the memo fields. Then down arrow through the frx and read what shows in the memo. Do this for each memo field. Sometimes seeing things out of context will help you spot the typo.

Good luck!


>Help. I've been working on a report for several days and it worked pretty well, then I decided to fix it...you know the story...I broke it but good.
>
>Somewhere I've introduced a bad expression (or something)that causes the diagnostic 'Command contains unrecognized phrase/keyword' to be displayed when I run the report. I've got so many controls and I've eyeballed them for anything weird, but cannot see the problem.
>
>The debugger does not seem to be able to debug inside of reports. Or am I missing something.
>
>Are there any techniques for hunting for coding errors in reports?