I think the behavior that being whacked about here is the obvious shortcomings of the report engine. The chosen print parameters, resolution, paper type... and even the printer choice are only valid for the current report (it appears that the report engine reinitializes its environment for each run).

Report 'runs' that are made up of multiple report specs (FRXs) will not respect the settings of any prior calls. I have a similiar situation where I have one report (only one thankfully) that is made up of three FRXs, a cover page, a summary page and multiple pages that support the summary data. So far I have not been able to work out a suitable solution to allow the end user to redirect and control this multi-part report using the native VFP report engine.

John is right-on about using an alternative engine to process this kind mess but we should add this one to the long wish list for the report engine (if its not already there).

If any one has a work around for this...