Your expectations are a long way beyond a report builder, any report builder. All of them will handle to design and layout of the reports you require, deciding on the layout of the report is up to the user designing the report, not the report builder software.
Storing the query and report code into a database is up to you to build. I have done all of the above using a number of reporting tools over the years so there is nothing new about your requirements. It will require you to a lot of work managing the infrastructure.
You will not need to create your own report designer, use one of the commercially available ones.
Never underestimate the power of human stupidity
I have a function fired by a buton to select an entire row of checkboxes of a datagrid and set them with the same value (true or false), similar to the excel filters. If all checkboxes of the row are true than if I click the button, they all become false, otherwise they all become true. But it only works when all the checkboxes are simultaneously true or false, if one of them is true, they all become false instead of true as it was supposed to, like in excel filters. This is due to the last part of the code that is commented which is not throwing the expected result. Can anyone help to see the problem cause?
1. why start at 7:7 (i and j)? Why go until grid_lic.ColumnCount -1 instead of grid_lic.ColumnCount?
2. Your i and j iterate through columsn onlyl not through rows at all.
3. Why do you set that CurrentRow.Cells to false or true?
4. Why the double statements (Convert.ToBoolean...)?
5. The Convert.ToBoolean seems un-needed
6. You need to first check ALL cells to see if they are all true or not, so that you'll know how to set them
7. Then, once you've done 6., you have to do a simple for..., and set each checkbox to either false or true (what you computed at step 6.)
-- Log Wizard - a Log Viewer that is easy and fun to use!
Reposting your question in a general forum will only serve to annoy the people who answer questions here, because you're duplicating work. Particularly so when you have completely ignored the advice you were given in response to your previous post!
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
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?
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)
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
8) Parent-child reporting