visual studio .net setup: I am using VS.net 2003 with VB. For reasons I have not yet identified my
right and left arrow keys no loger move an object on my forms. I am using
Winforms. If I place a field or button on the form, for example, and press
the right arrow key or left arrow key, nothing happens. As far as I know
the keyboard is working in all other respects and in all other programs.

Does anyone have any idea what's going on?

Hello Woody,

Thanks for your post. As I understand, the problem you are facing is that
you cannot move controls in a form with arrow keys. Please correct me if
there is any misunderstanding. I now share the following information:

1. Please right-click on form and/or controls and check if the "Lock
Controls" menu are toggled.
2. Can you move the controls with the mouse?
3. I suggest you to add a new form and see if the problem still occurs to
the new one.

If the problem persists, could you post a simple project which is able to
reproduce the problem? I will be glad to check it on my side.

I look forward to hearing from you.

Have a nice day!

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Thank you for responding.

[quoted text, click to view]

I created a new form and the problem persists. I can not move a button, for
example, with the arrow keys.

[quoted text, click to view]

Well, as I said, I simply created a form from scratch and placed a textbox
control on it and the arrow keys will not move it. I suppose if you do the
same on your machine the arrow keys will move the text box. If you want me
to send you my simply form I will try, though I don't know what the process
is.

It seems to me that the problem is program specific. That is, somehow, it
would appear, I have set some switch in VS (VB) that has turned this
capibility off. Arrow keys in all other programs seem to work fine. Is
there some sort of global VS/VB setting I may have inadvertantly changed?

Tian,

After sending the above message I made a discovery. The problem seems to
manifest itself only when my keyboard mappings are set to Visual Basic 6.
That is, when I change my keyboard mappings to Default, the problem goes
away.

Is this by design or is it an anamolie? Would you find out for me?