output from call (GRX)

[GCC Consulting]

> -----Original Message-----
> From: 
> filepro-list-bounces+gccconsulting=comcast.net at lists.celestial
> .com 
> [mailto:filepro-list-bounces+gccconsulting=comcast.net at lists.c
> elestial.com] On Behalf Of Bruce Easton
> Sent: Monday, December 18, 2006 1:23 PM
> To: filepro-list at lists.celestial.com
> Subject: RE: output from call (GRX)
> 
> Chris Sellitto wrote:
> > Monday, December 18, 2006 12:00 PM
> >
> > > >Scott Nelson wrote:
> > > >Is there limits to the call command from an input process?
> > > >I am trying an output process and it does not seem to print.
> > >
> > > >Scott
> > >
> > > Scott,
> >
> > > Calling an output process from clerk will work just fine. 
>  However, 
> > > how does it know what to print?
> >
> > > You will need to put a FORM "nameof form" command in the 
> call table.
> >
> > > You can make it conditional by checking @sn ne "" to see 
> if you are 
> > > in clerk or report.
> >
> > > Remember, it would also be possible to print different forms -
> > one after
> > > the other - in clerk using this.
> >
> > > You could print a sheet of mailing labels by using FORMM and 
> > > repeating it 40 times (or whatever fills a page).  Use 
> FORM on the 
> > > last label and it will close the print job.
> >
> > > One feature I always hoped for in filePro would be an 
> output process 
> > > that could print different forms, easily, in one pass.  
> It is a very 
> > > hard thing to do now and it would be so easy if you could 
> just issue 
> > > a form command(s) as you passed each record.  Not sure why they
> > never did it.
> > >
> > >Nancy
> >
> >   I would love to see this as an added feature as well Nancy, how 
> > about anyone else?
> >   I could have used this feature last week as a matter of fact.
> >
> > Christopher Sellitto
> 
> That sounds very useful, but I wonder if this were allowable 
> and even just two different forms were present, how much 
> slower the process becomes.  I would think there must be some 
> calulations/printer_driver_mappings/etc.
> that are now done by d/rreport only once to prepare output of 
> a "normal"
> d/rreport print job that would have to be considered and done 
> for each record.  If this is true, then maybe this feature 
> could be added, but would only be exercised when some switch 
> is turned on for it (and that you could use this for small 
> print jobs).
> 
> Also, being that you are suggesting different formats, would 
> you expect them to be available with the full set of options 
> presently available?  For example - a print job with varying 
> destinations?
> 
> Bruce
> 
> Bruce Easton
> STN, Inc.
> 
When printing from clerk using form, it is necessary to do all of your
"report" processing in clerk.

What I usually do is cast my dummy fields in the auto process table and then
use a call to the processing table that does sets these fields. Then I run
formmm or form which ever is appropriate.

If one is printing orders/invoices and has a form created, you will know how
many detail line can be printed per page,  you could count the detail lines
to print, the divide my the number of details lines on the page.  This will
tell you how many pages will be printed.  This allow you to print page N of
NN on the page, a sub-total etc until the last page is printed.

Of course, the are other methods of printing from clerk.

Richard Kreiss
GCC Consulting