@entsel??

[Scott Walker]

Dennis,

@key? THIS LOCKS THE RECORD.
	Put up your browse lookup and pick the script you want to run and
put it in variable named 	"Script_To_Run".

	Then "end".  At that point the record IS UNLOCKED


At this point fp hits @ENTSEL processing.

	The record is NOT LOCKED during @ENTSEL.

	If Script_To_Run variable contains a value, run the appropriate
script.
	
	Then clear "Script_To_Run" variable.

	Then "end"


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 Dennis Malen
Sent: Monday, December 06, 2010 10:26 PM
To: Kenneth Brody
Cc: filepro-list at lists.celestial.com
Subject: Re: @entsel??

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?

I understand that every time I use a browse that the record is locked out. 
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.

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 9:55 PM
Subject: Re: @entsel??


> On 12/6/2010 8:43 PM, Dennis Malen wrote:
>> Recently we instituted the use of an @key which pulls up certain scripts
>> (with the use of a browse screen) that are chosen by the user. This 
>> script
>> may remain on the user screen for 5 minutes or more. When we are running
>> reports the report selection stops at the various records that the users
>> have pulled up a script (one of the browse choices). It is not until the
>> user releases the script that the report can continue.
>
> That's because you're in update mode the entire time, and the record is 
> locked.
>
>> Is there a way that @entsel can be used in some way to avoid the problem
>> with the running of the report?
>
> A common way of doing that is to have the @key routine set a flag and end,

> and then @entsel checks the flag, and calls a subroutine to handle it. 
> Just remember that, because you're not in update mode, this subroutine 
> cannot change any fields in the current record.  (Though you can have the 
> @key do so if necessary.)
>
> -- 
> Kenneth Brody 

_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
Subscribe/Unsubscribe/Subscription Changes
http://mailman.celestial.com/mailman/listinfo/filepro-list