need help with dclerk

[Bruce Easton]

  On 9/9/10 12:57 PM, ken white wrote:
> --------------------------------------------------
> From: "Brian K. White"<brian at aljex.com>
> Sent: Thursday, September 09, 2010 12:47 PM
> To: "filePro Mailing List"<filepro-list at lists.celestial.com>
> Subject: Re: need help with dclerk
>
>> What required clerks form command that was not possible with reports
>> print command ?
>>
>> What required clerks form command that was not possible with reports
>> print command ?
>>
> formm "header"
> if somecondition1 then formm "fred"
> if somecondition2 then formm "barney"
> if somecondition3 then formm "howie"
> form "trailer"
> printer reset
> end
>
> Where each of the output formats represent a different format, dummy fields,
> pdf source.
> I would love it if dreport would support the above syntax in a processing
> only report, instead of forcing dclerk to be a report writer.
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
And even though the subject here seems to be report/clerk usage for 
non-interactive purposes, I think many developers use clerk as a 
starting place for output requests so that they can design browse 
lookups for capturing selection criteria - whether they wind up staying 
in clerk or calling a report process.

As far as speed comparison, I don't see how there would be a huge 
difference between clerk and report if both are following an index (and 
the lookup dash technique is being applied in selection processing).  
Maybe for very large amounts of data.  I guess clerk doesn't have to IO 
the temporary reporting indexes, but still - I don't think I've ever 
been disappointed with a report that uses lookup-dash in selection prc.

Bruce

Bruce Easton
STN, Inc.