Mathias,

I agree, this is the only solution I found.
I run the report for preview, display the preview. In preview's RELEASE I check for holes in the print range. If a hole is detected I do Listener.ONPREVIEWCLOSE(.F.), manage to dispatch the list of printable records to the listener and rerun the report without preview. The INCLUDEPAGEINOUTPUT will now check the list of printable records.

What I didnt like is that I have to run the report twice - some of them are complex (or slow)

Agnes

>There is probably a way to achieve that.
>
>What involves a design change - I have the page selection coming up before the reporting fires. Then in the IncludePageInOutput event simply return false to exclude a page from the output. Now the destination doesn't really matter.
>
>
>
>
>
>>Marhias,
>>
>>I would like to use other words but in the end yes.
>>
>>Agnes
>>>Are you trying to exclude page(s) after they have been previewed?
>>>
>>>
>>>>Hi All,
>>>>
>>>>How can I create a multirange report output to printer?
>>>>
>>>>What I like to do
>>>>I provide a click interface to (de)select a page or group of pages (preview container - this is the simple part). This will give a mixture of single pages and groups of pages to print.
>>>>I know how to dispatch the selection from preview to listener.
>>>>
>>>>My problem is that I have no idea how to suppress single pages from output.
>>>>
>>>>The event "IncludePageInOutput" that allows to in/exclude a single page will not run after the preview.
>>>>The help gives an example for the "OnPreviewClose" event that uses COMMANDCLAUSES.PrintRange* properties.
>>>>This one is fine as long as I print to my desktop printer. If I redirect the output to the department printer or to PDF I see that every DODEFAULT(.T.) in OnPreviewClose creates a new job to the printer. This will lend to more than one PDF files what is not the result I need.
>>>>
>>>>What solution do you see for that?
>>>>
>>>>TIA
>>>>Agnes