>As others have suggested, print the report to a file first and then save the _PAGENO variable to use when you print the report for real. One "gotcha" that you should be aware of is the fact that when you print to the file, it will use the current printer driver. This leaves the possibility that when you send the report to the print for real, and you prompt the user for the printer, they could pick a different printer. This means that they could pick a printer with a different printable area which could mean that a different amount of data fits on the two reports ... which means the page counts could be different.
>
>To avoid this problem, print the reports as follows:
>
>

>=SYS(1037)
>REPORT FORM xyz NOCONSOLE TO FILE junk.txt
>nPageNo = _PAGENO
>ERASE junk.txt
>REPORT FORM xyz TO PRINTER
>

>
>The SYS(1037) command will prompt the user for the printer up front so that both the dummy print to a file and the real print to the printer will use the same printer driver.

Cathy;

A nice bit of finesse! Presume nothing as your user will call you at 2 AM to say, “I (you) have a printer problem”! I will incorporate the SYS(1037) concept into my Report Class. I keep thinking I should place a copy of my Report Class in the Downloads section. I have six different Report Classes designed to “please” a user. That way I write less custom code when a user gets a “brilliant” concept as to how the report interface should function. :)

Tom