I see what your saying. Indeed it looks to be a bit tricky! It may be better to create some views and then base the reports directly on the views. Thanks for your example and help!
Actually, I am fine with creating individuals reports. The problem is the fields are not known at design time since the reports are based on dynamic recordsets. Essentially I want to use stored procedures called via ADO code as the source for the reports.
I would like to create a report in which the record source is created via ADO code and then set as the record source for the report. The problem I am running into is how to add fields to the report since the recordset is bound to the report at run-time and not design time. Is there way I can...