>The data environment of a report has an Init and a Destroy amoung other methods.

Variables created in these methods, unless specified as public are scoped to these methods. They are not visible outside of them.

I suggest a report wrapper for this. I may be wrong but I see a problem using the report as the only arbitor for this. The report itself creates a variable that it sets. In the Destroy of the report DE (or Summary band), it fires the report again based on this variable. It is going to try and set the same variable condition to fire the report again the next time it runs the report. What is the influence that determines if it should fire again? You say the criteria to run the report again can only be determined from inside the report. See if it can be determined from outside, then do the second call from outside.

Just my $0.02.