Hi,
Maybe I just reinvented warm water… but just in case not… a possible tip :).
Ever been coping with those reports with too many wide columns to fit your page width?
If you have referring keys to related tables or code tables behind those wide columns, this might be a way to save some ‘band’width:
– use the ID/code (value) in your main report’s column(s);
– create explanatory subreport(s) with the ID/code + relevant descriptive fields at the end of your report, preceded by e.g. ‘Legend – explanation of … codes:’
Example…
Original report:
Task Company Info1 Info2 Info3 Info4
………………………………………………………………… …………………………………………. ….. ….. ……………. ….
……………………………………………………………. ……………………………………………….. ….. ….. ……………. ….
Redesigned report:
Task* Company* Info1 Info2 Info3 Info4
…… …….. ….. ….. ……………. ….
…… …….. ….. ….. ……………. ….
* Legend – explanation of (standardised) task and company codes:
Task Description …
…… ……………………………….. …
…… ……………………………….. …
Company Name Category …
…… …………………………………………… ………………. …
As these subreports are linked to the main report, they are limited to the tasks & companies relevant to this client.
If this is too obvious, let me know and I delete this post :). If not, I hope it can be someone of help.
Hasse
ps Struggling with the table layout function here: either the tables are only visible in my preview… or when using text mockup, it ignores the trailing spaces. Hope it’s clear though!
