![activereports 7 pageheader activereports 7 pageheader](https://i.ytimg.com/vi/TSUoEhueuoI/maxresdefault.jpg)
In Fixed Page Layout based designing, with every DataRegion, there is a provision to limit the Width/Height of the it using FixedSize property. The section based layout designing approach requires some coding in events to achieve the same – can count the number of rows using a counter in Detail_Format event and use enum to insert a new page after a particular set of rows. This will cater to needs, where there is scope to show few numbers of records of phone usage on the first page, which is meant for showing summary, and the application user can save page. It would have been nice to limit certain area of report that shows bound repeating data. If is because the section grows as per the records to be rendered in the row. In section based layout designing, it is difficult restrict a section to show limited number of rows from a table. This will result in a report with two different Page layout designs, displaying data for a single Customer, rendered in different ways.ĭefining a Fixed Area for the data to grow The good part is that both these pages are connected to each other. So in case of designing a mobile bill, the first page (as ) can be created separately for showing summary, while a new page (as ) can be designed to show list of calls using a Table control. A Fixed Page Report lets the designer design multiple page based layout in a single reports(see image below). Can this be done in a simpler fashion using Fixed Page Layout designing approach using ActiveReports Developer 7.0 tool? Creating multiple layout designs in a single report using ActiveReports Developer 7.0ĭesigning a report with multiple layout designs is made easier with Fixed Page Layout, also known as FPL, introduced in ActiveReports Developer 7. Or design two different reports with two different designs and then print them separately. There will be one subreport to show list of calls (usage), and it will be called from the master report, which will show the summary of usage & billing information. If this has to be designed using section based layout approach, then it requires to implement as ‘Subreport’ (where each design layout requirement is built in different reports, and later all these subreports called from a master report). If this kind of layout has to be designed, this means will require multiple layouts in a single report. And it again ends with summary on the last page. The usage details, usually spills over to multiple pages, and mostly in columnar format. If there is any space available, it will show the usage details. For example, the first page of the report will have summarized usage detail, and billing amount.
![activereports 7 pageheader activereports 7 pageheader](https://rishblogs.files.wordpress.com/2012/01/progressbar.jpg)
This kind of report generally composed of different designs in a single report, and it is rendered in different ways on different pages. Now, let’s talk about a standard Mobile bill and the statement. There maybe other sections like Page Header or Page Footer, and that too may have some bound/unbound textboxes/containers and this section layout will result in similar kind of pattern while rendering the pages. And, if the Detail section has 5 textboxes/containers mapped to the columns of the table, it will render the data as the textboxes/containers are laid out in the section. Yes, this is because the containers with the Detail section will be rendered for all the rows of the bound table. If we analyze the report with respect to layout, will notice that data is rendered in certain pattern. When the report is rendered, it generate pages, and display the data from the table in each mapped container within the report and this data flows over from one page to the subsequent one, till the data from last row from the table is displayed. Let’s take up a standard Mobile bill with usage statement as an example, and walk through problems/workarounds of Section based layout designing also talk about another designing approach, known as Fixed Page based Layout designing.Ī report is bound to a database table, and has fields/containers mapped to specific column of the table. These kind of workarounds maybe easy to design (to develop the layout), but it is not that easy when it’s been execute. There are some scenarios faced in day-to-day report layout designer’s life, where workarounds has to be used in Section based designing approach to achieve specific layout based requirements. Designing a report layout within sections is a common way, and the easiest too, to show data in a printable form. When we think of designing a layout for a report, using any Report Designing tool, the designing approach is based on section, like Page Header, Group Header, Detail, etc hence this kind of designing is known as Section based layout designing.