@entsel??

[Dennis Malen]

I am responding to both Scott's and Ken's post responding to my question. 
Thank you again for your responses.

After having read both together I believe I understand the approach that 
should be taken which I will attempt to explain.

The first segment of the processing involves the @key. Once that is pressed 
by the user a flag (dummy field) is created. Once the flag is populated in 
@key the processing is ended and any further concern of locked record has 
now been eliminated.

The next part of the processing resides in @entsel. Once the @key has 
released the record the processing will move to @entsel where it will look 
for the value of the flag created in the @key processing. Once that flag is 
encountered the processing moves (goto) to the browse lookup processing that 
use to be in @key (which initially caused the locked record).

Once the @entsel processing (browse processing) is initiated the concern 
about locking the record has been eliminated again and the script can remain 
on the user's screen without the fear of locking the record.

Hopefully I got it right.

Dennis Malen
516.479.5912
----- Original Message ----- 
From: "Kenneth Brody" <kenbrody at spamcop.net>
To: "Dennis Malen" <dmalen at malen.com>
Cc: <filepro-list at lists.celestial.com>
Sent: Monday, December 06, 2010 11:30 PM
Subject: Re: @entsel??


> On 12/6/2010 10:25 PM, Dennis Malen wrote:
>> Ken,
>>
>> Thank you for your response.
>>
>> I do have a question as to what flag I would be putting in place in the 
>> @key
>> and end the process. How do I identify processing in @entsel that will 
>> check
>> periodically the processing in the @key?
>
> You can make up any flag you want.  Set it to a non-blank value in @key. 
> Then, in @entsel, check to see if it's non-blank.  If so, clear it and 
> execute your subroutine.
>
>> I understand that every time I use a browse that the record is locked 
>> out.
>
> Huh?
>
>> Does the processing which periodically checks @key also temporarily lock 
>> the
>> record and then release it once the "end" statement is encountered? Would
>> this be similar to using a browse lookup and having the browse window 
>> remain
>> on the screen after the processing was ended.
>
> What do you mean by "periodically checks @key"?  When you press a key, the 
> corresponding @key, if any, gets executed.
>
> [...]
>
> -- 
> Kenneth Brody