>Is there an easier way of knowing the exact code that has caused an error when the error occurs in the Report Designer ? The Report Designer is very poor in guiding you to the error code.
For debugging purposes, you can MODIFY REPORT, and then run the report from the report designer. This will get you to directly to the report object that has an invalid expression, for instance.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
