@entsel??

[Dennis Malen]

Craig,

Thanks for the feedback. I don't think that will be necessary in my 
situation as the users are just reading scripts. No information is being 
changed or updated in the record they are sitting in.

Dennis Malen
516.479.5912
----- Original Message ----- 
From: "Craig Tooker" <craig at cwtsoftware.com>
To: <filepro-list at lists.celestial.com>
Sent: Tuesday, December 07, 2010 5:20 PM
Subject: Re: @entsel??


>
>
> On 12/7/2010 10:23 AM, Dennis Malen wrote:
>> I am responding to both Scott's and Ken's post responding to my question.
>> Thank you again for your responses.
>>
>> Snip
>>
>> 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
> No offense intended but remember that while the code will run with the
> record unlocked, it's up to you to lock the record again before you make
> any changes to real fields in the base file.  If all your changes are in
> lookup records you have stated the situation correctly (although, of
> course, those lookup records need to be locked before changes are made.)
>
> Craig
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list