@key function

[Richard Kreiss]

> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> Sent: Wednesday, February 23, 2011 11:01 AM
> To: rkreiss at gccconsulting.net
> Cc: 'filePro mailing List'
> Subject: Re: @key function
> 
> On 2/23/2011 9:47 AM, Richard Kreiss wrote:
> > Windows server 2008
> > Workstation: Win XP Pro
> >
> > Received a call from a client's office manager this A.M>  telling me
> > the @keyO function was not working.
> >
> > I received an email from her boss saying that the function worked on
> > his computer.  When I tested the function through terminal server, it
> worked.
> >
> > /Ken define Not work
> >
> > Not work - nothing happens - the popup update fails to come up
> >
> > /ken define not working
> 
> :-)
> 
> > 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

> 2)  The office manager is running a different processing table.

No, worked is other sessions on her computer.  Option called from a menu

> 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.  

Richard

> 
> --
> Kenneth Brody