I think that your problem is one that comes from let's say a sales transaction file. You select records for a certain product from the file and run a report. But, if there were no sales of that product in a particular region there won't be any records to print in the detail section of the report for that region. You have to insert records with 0 sales into the RecordSource for the report. These records would be just dummy records with 0 sales but they would trigger the report page as you wish.
Example: I have created a table called tblSales. Fields: Region Text 5, ProductID LongInt, SaleAmt LongInt
I created another table called tblRegions. Fields: Region Text 5, RegionDescription Text 50.
The tblSales is your transaction table that indicates the sales by region and productID. The second table is just an informational table of all of the logical regions that you want to be reported on in each report.
The RecordSource of the report will now be based upon a UNION query of the two tables. This query will take all of the selected records from the tblSales and match by Region to the tblRegions. If there are any Regions that don't have any sales then a zero Region record will be created for the selected ProductID.
SELECT tblSales.Region, tblSales.ProductID, tblSales.SaleAmt
FROM tblSales
ORDER BY tblSales.Region
WHERE tblSales.ProductID = 123
UNION
SELECT tblRegions.Region, 123 AS ProductID, 0 AS SaleAmt
FROM tblRegions LEFT JOIN tblSales ON tblRegions.Region = tblSales.Region
WHERE (((tblSales.Region) Is Null));
Now we will have to adjust this to your situation with a legitimate criteria selection process and new table and field names. Get back to me and see if this won't work for you. Bob Scriver