Using dynamic formatting does avoid the messiness of nested controls and there's a great deal of flexibility in what you can do. We also set 90 in our app config. A bigger gotcha with going to 90, IMHO, is that you may need to tweak report objects to render properly; for example, text boxes with numeric values may need to be widened slightly.
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Paul Newton Sent: Tuesday, June 13, 2017 7:05 AM To: profoxtech@leafe.com Subject: Conditional formatting in reports
Hi all
I have always used the approach to be found in Help\Samples and Walkthroughs\Samples\Solution Samples\reports Solution Samples\Use Conditional Formatting in a Report Sample
However having sometimes three or more overlaid field controls with different Print When conditions can make report maintenance a PITA. So I have been looking at dynamically formatting report controls and in many ways this is a much neater approach and certainly makes report maintenance a lot easier.
The only drawback (and it is potentially a show stopper) is that in our situation we cannot guarantee that the end user will be using ReportBehavior 90.
So I was wondering what other people do:
1. Do you use conditional formatting with multiple controls or dynamic formatting with a single control? Or sometimes one and sometimes the other? 2. Do you force ReportBehavior 90 so that dynamic formatting will always work?
BTW the reason that some users prefer to use 80 is because the report is rendered page-by-page and with large reports there is very little delay between calling the report and having the first page rendered. With 90 there can be a very considerable delay before the first page is rendered.
I would be very interested in other people's thoughts.
Paul Newton
[excessive quoting removed by server]