This report definition is only used to generate the page counts by grouping; the file it creates is erased immediately. I realize that it is theoretically possible that the printer choice on any individual workstation at the time this data is sent To Printer or Preview could render the data slightly differently. If that were to happen, the page count for a particular grouping could be off by 1. The chance of this is so slight that I am willing to take it for the sake of being able to offer 'Page 1 of 3" when needed. I do use a slightly different report definition when the data is finally sent To Printer and/or Preview. That definition has a Report Title Page listing some additional information (including a count of total pages) and doesn't call the udf() in the Group Footer.

This whole process--and the extra hours it has cost me-- is sleight-of-hand just to get the page total by grouping. I can’t charge the client for figuring out that Report To File generates errors if you don’t first Set Reportbehavior = 80 and then use the ASCII clause on the Report command. That gets chalked up to 'learning experience.' I've been using FoxPro since 1.0 was in beta and there are still things to be learned <g>.