I have a form which displays a single (parent) record. The body of the form is a tab-panel with a tableview of child records, which could be quite numerous (e.g. 200).
All’s well till I try to print the form. Whatever I do, I can’t get the printed form to list all the child records in the tableview. I.e. I want the tab-panel to expand over multiple pages to display all the child records.
Is there some special magic I’ve missed or am I attempting the impossible?
Jan Blok:
Tabpanel printing is already very limited (see manual), printing a tabpanel should be avoided.
OK, then what alternative strategy do you suggest? (preferably not a portal, please)
Jan Blok:
(We always wonder the use of printing a tabpanel?)
Hmmm… I thought I just gave an example: growing to print a long tableview over multiple pages. On reflection, if a tabpanel can’t be grown to print all records then I can see that this line of thought won’t be very useful
HJK:
set print-sliding property of the tabpanel to:
allow height to: Grow
That was one of the first things I tried - unfortunately it only resulted in a print of the tableview partially (i.e. too short to display all records) and including scrollbars.
General rule of thumb when printing related records is to use a form based on the child table.
The form is list view and the header/footer contains any required related detail from the parent record.
Thus from the parent record you will isolate the foundset of related records and go and view them using the afformentioned form, preview/print and then return to original form.
By physically moving to a list view based on the child table you have a print format which then can flex with the number of related records and can use the parent record detail via a relationship back from the child to the parent.
We currently are printing from the 'parent’record using a growing portal set to multiline and allowed to grow in the body part. Thus we manage to output rather complicated reports.
I think this is the only alternative if you do not want to print from the related (children) form, which method remains easier if you have to manage sub totals and other summaries.
I ended using a listview form based on the child table, and putting a tab-panel (with form related to the parent) in the titleHeader. this got me pretty much everything I needed.