>A Bad news for you.
>The value of nKeyCode May Various from RUN-TIME and development time.
>
>For example, ALT+TAB (RUNTIME value is 15 but development time is -400!)
>So, your Keypress event handling need to mention more value to concern.
>
>and you need to check out the nShiftAltCtrl value to ensure the key-in is Arrow key.
>
>You're better to make a dummy project and generate that quick form into exe,
>so that you can check out the value in both run-time and development time.
>
>For another way to do: ON KEY LABEL..
>it will be global setting and you need to add more code to disable it when form not activate..
>Otherwise, expected action or effect will occur and make the application NOT stable.

Ok, I'll take a look at this. However, I have found a workaround for my specific case and I do not usually use ON KEY LABELs except in extreme situations as they are processed out of the event loop and can cause unusual problems. Also, some key combinations, like the ALT+TAB you mentioned is a Windows reserved key stroke. I generally try to avoid these anyway as I do not like to overide Windows OS processing unless really necessary.