need help with dclerk

[Bruce Easton]

  Yes - you should be able to do what Scott describes below, first 
relocating to the desired record with lookup dash, then substituting 
your entire form call [including any processing that may fill dummy 
fields, etc. prior to actually using the form or formm command(s)] - all 
within @entsel processing and then an "exit" when done.   If you are not 
necessarily interested in a record in the current file (say you're just 
on a control file record that you are not reporting against, and looking 
up to the file that you're reporting against), then @menu would be 
easier.  But I'm assuming here that you are passing a record # of the 
currently file that you want to report against, so @entsel for that purpose.

Bruce


On 9/8/10 10:16 PM, Scott Walker wrote:
>
> -----Original Message-----
> From: Scott Walker [mailto:ScottWalker at RAMSystemsCorp.com]
> Sent: Wednesday, September 08, 2010 10:10 PM
> To: 'Fairlight'
> Subject: RE: need help with dclerk
>
> Try using -xe
>
>
> Docs say:	Begin processing execution at input label @ENTSEL, skipping
> IUA menu.  Use "lookup -" to position to a record, otherwise IUA menu will
> de displayed when @ENTSEL is complete.
>
> I tried it.  In @once I used "lookup -" to position to a record, displayed a
> show statement, and then hit it with "exit".
>
> Seems to work,
>
> Regards,
>
> Scott
>
>
>
>
>
>
>
> -----Original Message-----
> From:
> filepro-list-bounces+scottwalker=ramsystemscorp.com at lists.celestial.com
> [mailto:filepro-list-bounces+scottwalker=ramsystemscorp.com at lists.celestial.
> com] On Behalf Of Fairlight
> Sent: Wednesday, September 08, 2010 9:48 PM
> To: filePro Mailing List
> Subject: need help with dclerk
>
> I knew this about a year or two ago, but I really rarely use clerk in an
> automated context, preferring report for my automated tasks, specifically
> because it has the -sr flag to jump to a record and sit there.
>
> Unfortunately, what we have is the need for processing to use FORM, which
> doesn't work in report.  So clerk is a must-have on this one part.
>
> We have processing that works.  It's in @ONCE processing.  It'll exit.
> It's -getting- to the @ONCE that's being problematic.
>
> Currently we have:
>
>       dclerk database -s0 -z processingtable -rx passedvalue
>
> The problem is that clerk hangs at the "Record Number, Scan for Records,
> Add Records, etc." menu.  I added -xig to use index G, which gets me a
> little farther along, but prompts me for index data to search for.  Tried
> adding -xe to drop to @ENTSEL, but that didn't actually work.
>
> Honestly, I don't know how to drop straight to a record (ANY record will
> do, seriously!) in clerk so that it executes the @ONCE processing.  I know
> I'm missing something simple, but I can't remember it, and neither can the
> actual fP programmer.  I figure I'll have the response here in under an
> hour if I just ask, so I'm asking.
>
> And no laughing!  :)
>
> Thanks in advance!
>
> mark->
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>