Trapping @keyB processing

[John Esak]

>
> >
>
> John, once again you mis-understood, and once again
> you seem to be attacking me for no reason.
>
> I NEVER SAID TO USE @KEYB!
>
> In fact I said to make sure he removed the @keyb.


I know and saw what you said. It just did not answer the question which was
being asked. Please see my precise 'cut and paste' of his question in
another message. He asked if @keyB processing could do both the standard
browse and also his own special "B" code. It can't, and I'm sorry you think
it can... and didn't even take the time to test. Unfortunately, I read the
question as it was written... not as I wanted it to be.

As I said in my private note... I'm not attacking you. Never have. These are
just simple words... and yes, I feel you should have taken the 3 seconds it
took me to demonstrate that what he wanted to do was not possible. There is
no question a work-around (of sorts) is possible using @entsel... again, I
would ask you to take the time to read some of the existing literature about
filePro that is available to anyone. You are always answering questions for
people, and that's great... I don't even care what anyone's level of
expertise is if they have a good answer. In this case, you chose to ignore
the question and suggest "something else" that would work. I think it would
have been fine if you first said, no what you want to do won't work, but try
this, but that is just my way, not yours. Sorry, I pointed out the obvious.

I'm also sorry you think I attacked you. In future I will not respond to any
message from you or any thread you participate in... that should eliminate
your problem with me.

John