@key function

[Richard Kreiss]

> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> Sent: Wednesday, February 23, 2011 12:46 PM
> To: rkreiss at gccconsulting.net
> Cc: 'filePro mailing List'
> Subject: Re: @key function
> 
> On 2/23/2011 11:47 AM, Richard Kreiss wrote:
> [...]
> >>>> 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'?
> >
> > I will, and I hate to use the word, assume that it branches to the
> > @keyO routine, which then does not run and she is returned to the IUA
> > on that record.
> 
> So, which of these do you believe the more likely?
> 
> 1 - Some obscure bug in filePro that not only prevents @keyO from being
> triggered when the user presses 'O', but only in some sessions.  And, not
> only does 'O' not trigger @keyO, but a MENU command which goes to the
> @keyO handler if the user presses 'O' will also not go to @keyO.
> 
> 2 - The processing in the @keyO handler can skip the POPUP UPDATE in
> some circumstances.


None of the above.

In reviewing the code in question, based on the login procedure, an
environmental variable is set with the user's login name.  

If the getenv("cassie") does not match the hard coded user names which can
run this option, the program ends.

The boss just advised me that in some cases when logging in, they are
getting an error message.  It is possible, based on this information, that
the variable "cassie" is not being set and access is being denied.

This would explain why when I accessed the file from the fp menu, and it
check getenv("username") for my login name, the routine ran.

The problem was I did not have all of the pertinent information.

Now I need to see why she had access from some of her logins but not others.

Richard