Trapping an Update

[Kenneth Brody]

On 12/5/2010 11:30 AM, Boaz Bezborodko wrote:
> On 12/4/2010 7:55 PM, Kenneth Brody wrote:
>> On 12/3/2010 11:00 PM, Boaz Bezborodko wrote:
>>> I'm sure that many of you probably already have this as a tool in your
>>> toolbox, but I figured I'd just share a simple way I used to trap an
>>> Update in a specific screen.
>> [...]
>>> Obviously totaling from within the record was not a good idea and I
>>> wanted to have this done from within @entsel which wouldn't lock the
>>> record. But I didn't want to change the look and feel of the program
>>> which entailed that people hit "U" to start the process. I was thinking
>>> of trapping "U" with an @keyU, but that meant that I would have to have
>>> a different line to jump to each of the other screens someone might want
>>> to update.
>>
>> I'm not sure what you mean by that last statement regarding @keyU.
>>
>> [...]
>>
> Ken,
> I've tried trapping @keyU and then executing UPDATE to go into update mode,
> but that didn't work right.

Well, given that you are already in update mode, I'm not sure what you 
expected UPDATE to to.  (The docs also say it's only for automatic processing.)

> I like the "DOKEY" suggestion and thanks for bringing it up since I had
> missed that one.

Or, given that you're already in update mode, just use SCREEN.

[...]

-- 
Kenneth Brody