I don't know which one you're talking about exactly -- give me a bug number or an example or try it <s> with a case you know will fail.

I doubt this method will resolve your issue, if you're saying that this incorrect _PAGENO appears in printed output.

(If you're saying that the _PAGENO is incorrect when you do REPORT FORM NOCONSOLE, that is a different story and has nothing really to do with grouping, although I suppose it might become more obvious with grouping. )

This is not a workaround for *anything*, per se. It is a way of telling VFP's engine to format the output as it would be formatted to go to the specified printer, so that you get the same pagination, without sending that output to a printer or a file.

So if your _pageno is wrong when you print, I would expect it to be here as well.

To be absolutely clear, this method might have some problems with some printer fonts (because when you output to any window you're using different device fonts in that case and they might not be exactly perfect). Similarly, you can get different roundings because of different resolutions. I can imagine that, if you are using "start a new page with XXX space or less" this *might* make a difference.

>L<