I agree with Karen. For example, I have one report that would require
four (4) simultaneous links to the contact table and summaries from two
other tables. With a view this would be a nightmare. I create a
temporary table with all the data in it using one insert and multiple
indexed updates. It's a small program that is used for races, some of
which include children, so I have the CarID that contains all the
contactid's for Driver (child), Parent 1, Parent 2 and the car's sponsor
to link up, not to mention the charges for entry fee and parts and the
payments that are in two more tables. The table is 65 columns wide. The
report is very fast.
Albert
On 6/26/2014 7:21 AM, Karen Tellef wrote:
I can't answer you with a "for sure" answer, except to say that me
personally -- I do not base reports on temp views, ever. Since you
can create temp tables as easily as a temp view, why not just insert
the data into the temp table and call it a day? Just my guess that
basing a report on a table that already has the data you need in it
should be faster than asking RBase to evaluate a view row by row as it
is generating the report. I have no technical knowledge of the report
generator code.
Karen
