>>
>>crystal reports does. foxfire (as far as i can tell) doesn't.
>
>I remembered a "tip" in FPA (May 1995 issue, pg 19). The workaround was:
>
>He set up a user defined function first.
>
>Function SetPage
>nNumPages = _PageNo
>return ""
>
>In the report, he added an expression object that contained a call to SetPage() which is ultimately called everytime the page changed. But the last call would be the value you are looking for. To get this to work in Windows, the code given is:
>
>nNumPages = 0
>cTmpFile = Sys(3) + ".TMP"
>REPORT FORM filename NOCONSOLE TO FILE (cTmpFile)
>ERASE (cTmpFile)
>REPORT FORM filename NOCONSOLE TO PRINTER [or PREVIEW]
>
>However, the user did get to see the "Printing..." dialog twice. It's deja vu all over again.
>
>HTH

serious work around. i think i'd stick to crystal reports.