Well, that's a bit more involved than I had in mind....
I want the user to be able to enter the data with keystrokes as much as possible (without using the mouse). When entering the combo box, some of them will allow the user to scroll through the list using the down arrow key, while a couple will only scroll using the up arrow key. (Mouse arrows behave 'normally'.)

Any ideas why?


>Hi Neil.
>
>>> What determines how a combo box/drop down list box responds to the cursor arrow keys? <<
>
>Do you mean you want to trap for cursor keys and take some specific action? If this is the case, you can trap for them in the combo's KeyPress and take action like so:
>
>

>DO CASE
>   *** This is a down arrow
>   *** Check for nShiftAltCtrl becuase <Alt>+<DNARROW> will dop the list
>   *** by default so you may want to take different action in this case
>   CASE nKeyCode = 24
>      IF nShiftAltCtrl = 0
>         *** 'Simple' down arrow pressed
>      ENDIF
>  *** Up Arrow Pressed
>   CASE nKeyCode = 5
>   OTHERWISE
>ENDCASE
>

>
>Just remember that if you are over-riding native VFP KeyPress behavior, you will need to add a NODEFAULT after you do whatever it is you want to do after intercepting the keystroke.
>
>HTH.
>
>Marcia
>
>
>
>