Try ONLY using a key-others which calls your library routine.
This is a funny animal - once defined any keys you don't define
as doing the normal thing will call the key-others. I'd at
least define the key-exit to do the normal thing so you don't
get trapped with no way out of the form.
Chances are this will be slower than defining the keys you want
and using key-others to disable everything else.
> Hi everyone,
>
> We are just about to roll out our application and have to
restrict the
> keypresses available to the user. These will include such
things as saving
> records, moving to next block etc and I wondered if there was
a good way of
> doing this without having to put triggers which do nothing
for each of the
> keys we want to disable?
>
> Preferably we would like to have a procedure in a library
which looks at the
> key pressed, and acts accordingly. Any advice would be much
appreciated.
>
> Thanks very much in advance,
> Wicksey
>
>
>
>
--
This answer is courtesy of QuestionExchange.com
http://www.questionexchange.com/showUsenetGuest.jhtml?ans_id=6326&cus_id=USENET&qtn_id=6283
Received on Mon Oct 25 1999 - 20:57:52 CDT
