I was just playing...

rbuser

Hi Nard,

There I was just playing with some reports and thought to myself,
'self'. 'Would the report be anymore efficient if I didn't have all the
table's fields in the table fields for the report?'

So I looked at the report I was playing with, includes a sub-report,
and pondered what fields to 'drop'.

It then occurred to me that it would be really great if the 'Fields for
Invoices', in my case' had an indicator against the fields that were
actually used in the report itself.

I mean. How hard can it be? Right?

So...
1. Is there any efficiency/performance benefit in ONLY having the
fields actually used in the report, in the reports table fields?

2. Can a 'check' mark or similar be added against those fields actually
used in the report?

Just some thoughts to myself....:-)

Ian

nicocizik

Hi Ian,

This would be a function of the database you are accessing. Theoretically,
if fewer fields are selected, the query will process faster but this is
something you would need to try. In reality, the performance increase may
be negligible.

If I understand correctly you would like the ability to toggle the
visibility of a field from within DADE like you can with the DataPipeline.
We will consider this for a later release of ReportBuilder. Thanks for your
feedback.


Regards,

Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com

rbuser

This is a multipart message in MIME format

rbuser

Hi Nico,

Apologies for the incorrect name.

Ian