Hi
I'm currently writing my first .NET app.
I've created a form, put a Report Viewer control on it, created my table adapter etc and can load an rdlc into it just fine. My report works as it should. However, I've discovered (I think) that I can only bind the Report Viewer control to the rdlc at design time. This means that for each local report I have to create, I have to create a new rdlc file (obviously!) AND a new form with its own Report Viewer control on it. This doesn't strike me as being the most efficient of methods, as the app will eventually have a few dozen reports. Ideally I'd like to load and bind the rdlc, table adapter etc into a single Report Viewer on a single form, at runtime, but fear I cannot do this.
Can anyone either resolve my dilemma or suggest an alternative reporting strategy?
Thanks for your help.
Xoqon
I'm currently writing my first .NET app.
I've created a form, put a Report Viewer control on it, created my table adapter etc and can load an rdlc into it just fine. My report works as it should. However, I've discovered (I think) that I can only bind the Report Viewer control to the rdlc at design time. This means that for each local report I have to create, I have to create a new rdlc file (obviously!) AND a new form with its own Report Viewer control on it. This doesn't strike me as being the most efficient of methods, as the app will eventually have a few dozen reports. Ideally I'd like to load and bind the rdlc, table adapter etc into a single Report Viewer on a single form, at runtime, but fear I cannot do this.
Can anyone either resolve my dilemma or suggest an alternative reporting strategy?
Thanks for your help.
Xoqon