@entsel??

[Kenneth Brody]

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