@key function

[Kenneth Brody]

On 2/23/2011 11:07 AM, Richard Kreiss wrote:
[...]
>>> To continue, I called the office manager and asked her if she was
>>> having this problem in all of the sessions she had open.  The problem
>>> was in 2 of the 5 sessions she had open.  She is normally accessing 5
>>> different files, one in each session.
>>>
>>> My question is, what might cause an @key function to fail to execute?
>>
>> In no particular order...
>>
>> 1)  The "O" key is broken.
>
> No, worked on other computers in and out of the office

Yes, I saw that.  I was being facetious.  (Though it is a possibility, 
however unlikely.)

>> 2)  The office manager is running a different processing table.
>
> No, worked is other sessions on her computer.  Option called from a menu

And you are 100% certain that the 2 windows where it "doesn't work" are 
running the same menu and the same menu choice?

>> 3)  It _is_ executing, but something in the processing itself prevents
>>       the popup update from appearing.
>
> I was able to run @keyO from terminal server on one of the records she was
> having a problem with and the @keyO function worked.
>
> One other point, @keyM brings up a menu listing all of the @key function
> available.  I had her run  @keyM and the menu came up.  When I asked her to
> press<O>, the menu closed but nothing happened.  That is when I tried the
> same thing from my login.

And what does the MENU command do when you press 'O'?

Have her turn the debugger on in one of the sessions where it's not working, 
and single-step the processing to see what, exactly, it's doing.  (And my 
guess is that #3 is the answer.)

-- 
Kenneth Brody