Record being updated

[Bruce Easton]

Just relocating the current record seems to answer that, Rami, although 
I will point out below some unexpected behavior.  In this test case the 
system command is for *nix:

   1  -------   -   -   -   -   -   -   -   -
            ? If:
        Then: end
   2  -------   -   -   -   -   -   -   -   -
@entsel? If:
        Then: cx="echo \"press a key to continue\"; read ans; "
   3  -------   -   -   -   -   -   -   -   -
djwuzy ? If: dj eq "Y"
        Then: system cx
   4  -------   -   -   -   -   -   -   -   -
        ? If: djwuzy
        Then: dj=""
   5  -------   -   -   -   -   -   -   -   -
        ? If: djwuzy
        Then: lookup - r=@rn -n
   6  -------   -   -   -   -   -   -   -   -
        ? If: djwuzy and @cd eq ""
        Then: errorbox "rec deleted whilst sys cmd running"
   7  -------   -   -   -   -   -   -   -   -
        ? If: djwuzy and @cd eq ""
        Then: pushkey "X"; end
   8  -------   -   -   -   -   -   -   -   -
        ? If:
        Then: end
   9  -------   -   -   -   -   -   -   -   -
@keyj  ? If:
        Then: dj(1,*,g)="Y"
   10  -------   -   -   -   -   -   -   -   -
        ? If:
        Then: end


On line 7, originally I had just tried "If: djwuzy and not - ", but even 
though the record had been deleted from another test screen, the lookup 
- here subsequently still was successful, so I had to resort to testing 
@cd which did report as blank from the record having been deleted.


Bruce


On 10/21/14, 10:06 AM, Rami Mantoura wrote:
> I already use the entsel process but I did what you suggested and it sort
> of works.
> The problem I have is that it only works the first time on the record i am
> on.
>
> Here is the logic.
> I use @key? and open a browse. I pick a record and zoom to the record in
> the lookup. I finish the update and exit which then brings me back to the
> browse window. At this point I would either exit out of browse window or
> select another record.
>
> The problem is if I either exit out of the browse or select another record
> the @entsel does not occur again. Is there some kind of reset command I
> could use to invoke the @entsel?
>
> Thanks
>
> On Wed, Oct 15, 2014 at 6:30 PM, Kenneth Brody <kenbrody at spamcop.net> wrote:
>
>> On 10/15/2014 3:57 PM, Rami Mantoura wrote:
>>
>>> Hi All,
>>>
>>> I have a question regarding FP behavior.
>>>
>>> If you are using an @key??? and you "zoom" to another file it seems to
>>> lock
>>> the record even though you don't go into update mode. Is there a way of
>>> not
>>> having that record locked. The reason I am asking is because I need to
>>> post
>>> back to that record.
>>>
>> You entered update mode when the @KEY event was triggered.
>>
>> If you need to allow some other process to update the file, and your @KEY
>> handler won't make any changes, there are several solutions.  A common one
>> is to set a flag in your @KEY event, and then end.  Then, have your @ENTSEL
>> handler check that flag and do whatever you need done, such as your SYSTEM
>> command.
>>
>> --
>> Kenneth Brody
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20141021/55f40235/attachment.html>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>