Problem with dreport crashing

[Bruce Easton]

(inline responses - Bruce Easton, STN, Inc.)

Fairlight wrote Thursday, July 31, 2008 1:19 PM:
>
> On Thu, Jul 31, 2008 at 11:33:55AM -0400, after drawing runes in
> goat's blood,
> Bruce Easton cast forth these immortal, mystical words:
> > I haven't looked deeply at that code above, but two things
> > stand out to me at first glance.  You say this is a
> > selection processing table called by -v.  But you are
>
> That was a typo.  Both phonetically end in "ee" and I make that mistake
> when talking about them and even typing them.  I doublechecked the command
> and it -was- set to -v, not -z.  I simply mis-spoke here.

Well - I'm still a little confused, but I'll assume for now
that you are using a -v and that you intend it to be running
that code as selection processing, not output processing.

>
> > assigning fields and writing them with the write command
> > near the top. And you are using the print command at the
> > bottom.  I don't believe either of these are appropriate
> > for a selection table.  I have never used a selection table
>
> Well, -something- doesn't like what I'm doing.
>
> However, I can assure you that I regularly write fields in the control
> record upon which I sit in every top-level CGI processing table I write.
> Helps me keep track of when a slot was last used.  (If I see that the last
> time slot 13 of 14 allotted was used only a few months ago, no biggie...if
> I run a check regularly and that slot is always less than 3 days old, I
> know we're approaching our license slot limit and might have to adjust
> something.)

OK, I'll assume that the real field assignment in other cases for
similar purposes is doind exactly what you intend.

>
> I'll try a few things to try to resolve this.  I'd swear I was told to use
> print.  Maybe it was meant to be from output processing, not the selection
> table (where I'd personally expect select, although that did nothing).

Yes, PRINT command within output processing, to tell filepro to output
the section that filepro thinks it is on (data section, grand-total
section, sub-tl break section) at the time that it is encountered.
(And if used at all in the output processing, then it must be included
and executed in all different types of section where you wish to output.)

>
> One question I do have...
>
> If NO reports match, I'm not going to get any report.  It'll be blank,
> basically...as in, nothing will be generated.  I could force a field to
> read "NO MATCHES" and carry on with a print on a one-time only basis, but
> it'll then have the grand total for records printed as 1, not 0.  How does
> one get around this behaviour?  I want to at least get
> -something- printed,
> even if the detail lines are completely empty (I'd prefer "NO MATCHES" by
> far), but I need the total to be 0 in any event.  Suggestions?

Use @wgt0 in your output processing, and test number of records
selected (@ts) there to then issue desired code for the case where
no records were selected.

>
> mark->
> --
> "Moral cowardice will surely be written as the cause on the death
> certificate of what used to be Western Civilization." --James P. Hogan
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>