Situation: We've designed a decent looking Report page using the .NET ReportViewer (ASP.NET, RDLC) with a custom object from our object model. My underlying (and possibly incorrect) assumption was that if we bound a collection of custom objects to the ReportViewer/RDLC, the control would build a populated report layout for each object in the collection.
My past report experience has been with the MS-Access report engine, where binding a datasource to a report will result in the report layout being applied for each record in the data source. If the report layout spanned an entire page, for example, a populated report page would be built for each bound record.
Question: My colleague tells me that the .NET ReportViewer cannot function in the way I describe. Really? Please tell me he is mistaken? Any guidance on a solution or work-around?
Thanks in advance, -JR
NOTE: Original question title changed in response to clarifying answer.