I have a FR5 report that has two dynamically sized TfrxMemoViews. They start out about 20 high and grow as needed. Now I have a record that has more than enough data to cause the Memo to exceed the page height. How can I the data flow into a MemoView on the next page?
I have a FR5 report that has two dynamically sized TfrxMemoViews. They start out about 20 high and grow as needed. Now I have a record that has more than enough data to cause the Memo to exceed the page height. How can I the data flow into a MemoView on the next page?
OK. I could not get the DAC to work (professional Berlin) but that might not be necessary since i could open your report in the designer. First off - i have a sh*tload of FR reports deployed at my clients. Those systems are now so stable that i almost have not touched anything in two years time so my memory is a bit rusted and i do not have the time to test my suggestion but here goes;
ReplyDeleteOne of the things i had to spend some "learning-curvy" time on is the fact that you can place controls /outside/ of a /band/. I have never ever had to do that. I think you would use it for waterstamps and such things bound to a "physical" page. A hefty 10% of the "bugs" i have had to root out in my FR implementations has sprung from the fact that one pixel is outside of the band and FR judged the whole control outside of the band.
If i'm right - put all end everything into bands. The Band that you place your TfrxMemoView into (check the "Object Inspector Tree") will enable you to control page breaking in a way that seldom requires code. I have some agreements that are printed on two sides and putting the blank page so that agreement number 2 will print on an odd page required code. Also when trying to judge if a huge memo should start on the next page or be kept and the split requires some code. FRs notion of Master-Detail-Subdetail-4th Detail and Child bands are quite powerful.
So; first add a Master band, connect it to you data, put your control(s) inside it, check the "Allow split" and "Stretch" property of the Masterdata band. That should do it.
HTH,
/D
BTW, The DAC. I right-clicked on the connection component and edited the path. Seems the ini-file is ignored.
ReplyDeleteDany Marmur
ReplyDeleteThat did it,
I put a Master and Detail. The master shows the recipe name.
The detail has everything else. If too much data, it flows to a new page.
Super duper. Coolness. Thank you very much.