>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

Glad to hear that the problem is solved. I prefer to always build a single cursor, so I haven't really encountered a problem. Here right now we're using VFP8, going to switch to VFP9 soon. I noticed that several reports in the already built applications use relations. It may become a problem for us too when we'll switch, so at least I know about resolution for the problem.

Thanks again.