Report Builder in Visual Studio
-
So I wasn't sure whether to post this here or in the database section, but here it goes. I have a 'logbook' that I'm developing which is basically a simple message board. Where I'm drawing a blank is how to format the data coming out of the database for the printable report. The database is set up so that all the messages are stored with various headers and a parent/child structure in a single table. You can have multiple child replies to a single parent, but only 1 level deep. Where I'm drawing a blank is how to structure the data for use in the printable reports. Any help would be massively appreciated as I'm drawing a blank as to which direction to go with this. Here's the desired report structure[^] and the current data format[^]
-
So I wasn't sure whether to post this here or in the database section, but here it goes. I have a 'logbook' that I'm developing which is basically a simple message board. Where I'm drawing a blank is how to format the data coming out of the database for the printable report. The database is set up so that all the messages are stored with various headers and a parent/child structure in a single table. You can have multiple child replies to a single parent, but only 1 level deep. Where I'm drawing a blank is how to structure the data for use in the printable reports. Any help would be massively appreciated as I'm drawing a blank as to which direction to go with this. Here's the desired report structure[^] and the current data format[^]
From your post it is difficult to understand what you want to achieve or what the problem is. If it is a single table, I'm unsure what you mean with "how to structure the data". Linking the records seems (from your text) easy enough. What's the report for? What data should be on there? For whom is it? You're not asking for a report structure, or are you?
V.
(MQOTD rules and previous solutions)
-
From your post it is difficult to understand what you want to achieve or what the problem is. If it is a single table, I'm unsure what you mean with "how to structure the data". Linking the records seems (from your text) easy enough. What's the report for? What data should be on there? For whom is it? You're not asking for a report structure, or are you?
V.
(MQOTD rules and previous solutions)
-
So I wasn't sure whether to post this here or in the database section, but here it goes. I have a 'logbook' that I'm developing which is basically a simple message board. Where I'm drawing a blank is how to format the data coming out of the database for the printable report. The database is set up so that all the messages are stored with various headers and a parent/child structure in a single table. You can have multiple child replies to a single parent, but only 1 level deep. Where I'm drawing a blank is how to structure the data for use in the printable reports. Any help would be massively appreciated as I'm drawing a blank as to which direction to go with this. Here's the desired report structure[^] and the current data format[^]
I suggest you consult the documentation for the (Sql Server / Visual Studio) Reporting Services and do one of the "walk-throughs". That will take you through: 1) Starting the report designer / builder 2) Specifying a data source (I.e. database tables) 3) Selecting records 4) Fields to report on 5) Sorting 6) Formatting 7) Grouping 8) Parent-child reporting etc. Reporting Services Tutorials (SSRS)[^] Once you have something going, you can ask more specific questions.
-
I suggest you consult the documentation for the (Sql Server / Visual Studio) Reporting Services and do one of the "walk-throughs". That will take you through: 1) Starting the report designer / builder 2) Specifying a data source (I.e. database tables) 3) Selecting records 4) Fields to report on 5) Sorting 6) Formatting 7) Grouping 8) Parent-child reporting etc. Reporting Services Tutorials (SSRS)[^] Once you have something going, you can ask more specific questions.
-
So I wasn't sure whether to post this here or in the database section, but here it goes. I have a 'logbook' that I'm developing which is basically a simple message board. Where I'm drawing a blank is how to format the data coming out of the database for the printable report. The database is set up so that all the messages are stored with various headers and a parent/child structure in a single table. You can have multiple child replies to a single parent, but only 1 level deep. Where I'm drawing a blank is how to structure the data for use in the printable reports. Any help would be massively appreciated as I'm drawing a blank as to which direction to go with this. Here's the desired report structure[^] and the current data format[^]
I'm with Gerry on this, pick a report builder and use that, anything except Crystal Reports. We us SSRS and it does all you need but then so do ALL other reporting tools. Parent/Child structure are the bread and butter of reporting.
Never underestimate the power of human stupidity RAH
-
Thanks for the reply. I updated the original post with some pictures to see if that helps explain it.
Hello, Much clearer, thank you. I'm not sure what everyone has against Crystal Reports, I worked with it and never had any issues. I think from the other answers a quick tutorial is indeed a good idea. Many report builders allow grouping/summaries and even graphs on the fly. Playing with it is the best way to learn. Not sure about other reporting tools, but Crystal Reports allows basically two ways of fetching data. You select data from .Net and pass it to the report document allowing more dynamic control or (my favorite) you build a template and just pass some parameters from .Net to it. The report document will fetch the data itself and build the report. (advantage is that you can test the report outside your application) Concerning the report format I can only give the advice what I always do. That's asking yourself what is important. I use the 7 seconds rule. The first thing any user asks himself when seeing a webpage, a report, a document, ... is "What am I looking at". Attract their attention with showing what the report is about. The next 7 seconds are navigation. The user passed the first 7 seconds and now wants to know how the thing is constructed. (layout, where is which data, etc ...) After that you have their attention and only then will they look in detail. (PS: I say 7 seconds, it could be 3 or 5 or 2.45, but you get my drift) Hope this helps.
V.
(MQOTD rules and previous solutions)
-
Hello, Much clearer, thank you. I'm not sure what everyone has against Crystal Reports, I worked with it and never had any issues. I think from the other answers a quick tutorial is indeed a good idea. Many report builders allow grouping/summaries and even graphs on the fly. Playing with it is the best way to learn. Not sure about other reporting tools, but Crystal Reports allows basically two ways of fetching data. You select data from .Net and pass it to the report document allowing more dynamic control or (my favorite) you build a template and just pass some parameters from .Net to it. The report document will fetch the data itself and build the report. (advantage is that you can test the report outside your application) Concerning the report format I can only give the advice what I always do. That's asking yourself what is important. I use the 7 seconds rule. The first thing any user asks himself when seeing a webpage, a report, a document, ... is "What am I looking at". Attract their attention with showing what the report is about. The next 7 seconds are navigation. The user passed the first 7 seconds and now wants to know how the thing is constructed. (layout, where is which data, etc ...) After that you have their attention and only then will they look in detail. (PS: I say 7 seconds, it could be 3 or 5 or 2.45, but you get my drift) Hope this helps.
V.
(MQOTD rules and previous solutions)
