get clerk to act like report
Brian K. White
brian at aljex.com
Thu Apr 4 11:06:55 PDT 2013
On 4/4/2013 1:51 PM, Kenneth Brody wrote:
> On 4/4/2013 1:17 PM, Brian K. White wrote:
>> tldr: "-n"
>
> :-)
>
> [...]
>> Howie my secret personal resident ace in the hole filepro expert dinged
>> me with the clue.
>>
>> "-n"
>>
>> So my "input" process just has one single line:
>>
>> ---top---
>> call "mycalltable"
>> ---end---
>>
>> And my command line is:
>> rclerk file -z myinput -Sblankscreen -XS myselectionset -n
> [...]
>
> As long it's okay with you that this will update every record selected,
> it's okay with me. :-)
>
> BTW, is there any reason you don't just use "-z mycalltable"?
>
I am.
I though I implied that with
> But wait it gets better and you already knew it...
>
> Sure enough the call table also functions when executed directly by -z
> instead of call. This works:
>
> rclerk file -z mycalltable -Sblankscreen -XS myselectionset -n
>
> The one-line -z myinput above is not needed.
I guess I didn't specifically say I'm doing that now, only that I
discovered it works. Yes once I saw it works I'm now doing it that way.
As for update on each record... well at the moment I'm not writing
either on the standing records nor any of the lookups to other files,
but I will be later, so, update is ok. But good point. A real read-only
version would be nice but so would a lot of things. I'll live. :)
Normally this will run from regular interactive input, either from an
@key or some other trigger like @wlf or esc-esc, so update is already in
effect usually anyways.
If I have to do it in batches from cron also, then I think PFSKIPLOCKED
will be appropriate and reasonable behavior.
--
bkw
More information about the Filepro-list
mailing list