>>I have a report that deals with a single record. I want it to be a two page report, but _I_ want to say where the page break is. A few questions:
>>
>>Is there a better way to handle a report that is a single record report (and pre-processed data in memvars) ?
>>
>>How can I force a Page break?
>>
>>Any way I can control the print driver in code (I want to select duplexing, if it is an option) ?
>
>You may try to call a function which will return an empty string, but force eject:
>
>Function EjectIf
>lparam pcCondition
>if eval(pcCondition)
> eject
>endif
>return ""
>
>I'm not sure your report will reprint the header, though. Haven't tried this for a long time.

I don't know if that will work. In older (2.6 and before) if you did an eject in a user defined function, the report still had it's own internal counters for lines on a page, etc. This caused problems like getting only partial pages later on in the report, when the counters determined there should be an eject. AFAIK, there's no way to access those internal report counters. It may work OK in VFP 5.0, though, I haven't tried anything like that lately.