planning ahead - need advice

[john]

I^m trying to plan a new report - and need some advice on the best way to proceed____The scenario:__Parent table with 4 child tables and a couple of lookup tables__Each parent table and up to 5 child records for child tables 1,2, and 3 need to be on one piece of paper (or side if we consider duplex printing) The parent record page must follow a preset format (think State Government provided forms)____any additional child records from tables 1, 2, and/or 3 need to print out on additional page(s)- can be almost any format but a copy of page one^s format would be best____child table 4 needs to print each record on its own page____I can build my application to call seperate reports as needed however it would be better(?) if I can use a UDF to call the additional pages something like iif(chldtable2reccount > 5, run anotherreportpage,"") or maybe some other technique would be even closer to "best"____My application is designed for single record printing of the parent table 99% of the time, however on occasion the user will want to print a subset of records. I am planning on giving them a place to enter the key value for each record in the subset (in no particular order) and then run the set of parent records for them.____Also on rare occasions, the user will want a complete set of reports for every parent record.____No matter what scenario I forsee, I expect that either the table handling in R&R (with several thousand copies of the tables open at once) or the Windows print spooler giving up and heading south when any of these batch printing operations is called.____I^m sure I am not the only one who needs multiple pages for a single record and/or child records so ideas will be appreciated.____Thanks in advance____John

[kfleming]

I would design separate reports to be run sequentially as needed.____Kathleen__R&R Support