If I understand correctly, the solution to the problem was Naomi's message, not your reply to it. For the benefit of anybody who reads this thread, you may want to correct this, i.e., which message is marked as "solution".
>Bonjour Naomi,
>
>Thank you for your help. I tried the "classic" solution ( SET REPORTBEHAVIOR 80 ) but it doesn't work. I looked further and I noticed a very high network activity while the preparation of my report. My report was built around different files linked together with some "set relation to..." So I changed my approach and generated a single SQL cursor and I modified my report to reflect that change. This was the solution.
>
>I'm surprised how the "set relation to..." made a so big difference from one version to the other.
>
>Thanks again,
>
>Normand
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)
