I have an app listing the costs of our forklift fleet based on two separate Excel_files.
The output right now is a straight table with all the costs. It does not quite fit on the screen horizontally, so there is a scrollbar (when I print it in landscape_orientation, however, it does fit).
There is also a vertical scrollbar since there is more data than can be displayed all at once.
That might be key to my problem.
When I create a report with a filter so that there are only 2 lines of the table to display, all is fine.
When I create a report with all selections removed to have the complete list, it looks kind of weird. All columns of the table are squashed together in a very small area on the left and all the rest is blank ... Strangely, that 2nd report prints in portrait_format, although the settings are the same as in the other report, that is, landscape_format (I used that "copy datasheet from other report" checkbox).
Can anyone help me with that?
Thanks a lot!
Best regards,
DataNibbler
P.S.: No, I did not look closely - it does print in landscape_format all right, but everything appears very much squashed together.
- I add a line_ID in the "master_list" in the script - I load the other one with a WHERE EXISTS() clause, so there should be no gaps there.
- Then I create a secondary ID by grouping that into buckets of 10 or 12. I suppose that could be done with the IntervalMatch() function more elegantly than I can do it directly on the GUI.
- I will then tick the "serial printing" checkbox that is on the "selections" tab of the "report settings" in the report_editor and select that latter field
yes, that would also have been possible and maybe easier.
But I did it with the IntervalMatch() now. Now the last two reports look fine - they are now split into pages, with 10 line_IDs on each page. The one for one plant now is a bit longer than necessary because, due to the filter, there are not necessarily 10 lines on every page and so the nr. of pages is more than necessary. Here your method is probably better as it would be recalculated with every selection. I will try.
P.S.: No, that won't make it easier as I cannot select, for the "serial-printing" setting of a report, any fields that exist only on the GUI. So I'd have to make that in the script and again it would be insensible to selections.
Never mind. I guess it's good enough and there's tons of other work waiting, so I'll leave it at that for now.
