Hi Glen,
How about having more then one cursor ?
I mean like having one cursor (or table)
which is not driving any particular report itself but just
defines execution order, conditions ,chaining etc.

Then whole reporting task can be broken down into individual reports driven by their own tmp cursors and/or tables and executed according to parameters from that 'task driving' cursor.

Instead of one huge complex report with multiple detail bands, you can have menu small simple reports executed together but all being part of parent report/print job.



>I need to produce a report which will print totally different layouts based upon a data element in the cursor which is driving the report. I need to do this becase this is an application where the user expects to just go over to the printer and pull off a set of documents in order and use them without any further sorting or merging. We will need to produce something like merged sets of different documents in one run.
>
>My first idea is to create a loop which will act like this:
>

>scan
>  do case
>  case valueofreportcriteria = 1
>     report form type1 next 1 to print noeject
>  case valueofreportcriteria = 2
>     report form type2 next 1 to print noeject
>  case valueofreportcriteria = 3
>     report form type3 next 1 to print noeject
>  case valueofreportcriteria = 4
>     report form type4 next 1 to print noeject
>  endcase
>endscan
>report form endreport to print
>

>
>Clumsy to say the least. Any better ideas?
>
>Glenn