Tim and Brian,
Thanks for your detailed responses, a lot of food for thought there. In
particular I like the "simplicity" of Tim's "RV to file" option but that
maybe also achievable pinching a small part of idea from Brian's suggestion
and store the data to a new panel and then bring back into the report at the
end.
The report already has over 100 RVs and many of them are at least 2-3 pages
long. Due to nature of data and required manipulation many contain a heap of
Apply.Format calculations - so it gets busy in there (at my level :-).
The actual new data presentation that I need to appear at the end of the
report is not that onerous as RV formulas go. So I'm looking to try and
achieve without having to re-write the whole report - just make an addition
to the existing if possible.
I'll have a look at it over the next few days and weekend and let you know
how I get on.
Thanks again for your input.
Cheers
Colin
----- Original Message -----
From: "Tim Rude" <[email protected]>
To: <[email protected]>
Sent: Wednesday, July 30, 2014 3:46 PM
Subject: Re: [Dataperf] DataPerfect Report - Is this do-able
On 7/29/2014 9:16 PM, Colin Roberts wrote:
Hi All,
Been a while :-)
Wanting to modify one of my existing reports to produce a seperate
"cutting list" at the end of it.
Basically have 3 x user data entry panels
1. Order Entry Panel, 2. Door Calculation Panel, and 3.
Door Prehung Calculation Panel
Panel 2 is child of panel 1 and Panel 3 is child of Panel 2.
Currently Report is single level report based on Panel 1, with subreports
within Report body to show required data from Panel 2 and Panel 3. All is
fine and this report, with on-going modifications, has worked fine for
years.
Recently discovered supervisor in Factory has been manually producing a
cutting list for Door Frame jambs which is coming from the subreport/data
connected to Panel 3. He writes the data down manually in a slightly
different format with a couple of re-calculations.
Dataperfect can easily produce that data in his format within the
subreport. But..... What I would like to do is calcualte the cutting list
as each item is processed within the report but hold it over so that a
seperate list is printed at the end of the report containing all the
required data relating to Panel 3. Appreciate its easily achieved by
running a separate report that processes just the required data but that
does rely on remembering to print it. If the data required is stored in a
report variable for each item I can see no way of printing each items
data, line by line, in the final footer or at the end of the report
(Preferably on a new page).
So I'm looking at maybe Two level reports, parallel reports or, if
possible, a report within a report - so all the info required is produced
running just a single report only once.
Thought I'd draw on this wonderful resource to see if what I want to do
is do-able before I spend too many hours reading through Ralph's Book and
trying to figure out best approach.
Hope the above makes some sense - any pointers would be much appreciated
Regards
Colin Roberts
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/cgi-bin/mailman/listinfo/dataperf
Hi Colin,
Depending on how much data the 'cutting list' contains and how simple the
formatting can be, you might be able to accumulate all of the lines of
data for the cutting list into a single RV while your main report is doing
its thing. Then at the end in the final footer you could include a <Page
Eject> code and then print your RV as A0A0.
As I recall, I once had a report that created a huge CSV file of contact
info and then later I needed it to also create a second smaller file with
a specific subset of the data. I edited the original report to accumulate
all of the data for the second smaller file (which was a pretty good size
file too) into a single RV while the main file was being generated, and
then I printed that RV to the new file in the footer. I was actually
surprised at how well it worked and how much data the RV held. I guess
internally DP must treat a RV like a multiline text field, and lets you
put a lot of info into it.
Would something like that work for your situation?
Tim Rude
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/cgi-bin/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/cgi-bin/mailman/listinfo/dataperf
