Hi Jason,
>When I'm working in the dialog editor in VS.NET 2003, the arrow keys
>do not function. On other developers' machines that I've seen,
>the arrow keys move the selected object (button, static text, editbox,
etc.)
>1-pixel in the requested direction...
It appears your machine's VS.NET IDE has some problems, the arrow keys
should be used to move the selected object in the dialog editor, this
feature is by default and there isn't any setting in VS.NET to
change/disable it.
So in current scenario we want to know collect more information about this
issue, does this problem only occur from recently and have you found the
same problem with Windows Form Designer?
Thanks!
Best regards,
Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn
This posting is provided "AS IS" with no warranties, and confers no rights.
Jason P - 04 Aug 2005 14:09 GMT
Hi Gary,
> So in current scenario we want to know collect more information about this
> issue, does this problem only occur from recently and have you found the
> same problem with Windows Form Designer?
This problem is not recent. It goes back as far as I remember, at least to
VS.NET 2002. I just checked and the same thing does occur with the Windows
Forms Designer as well. The arrows keys have no effect on the selected
item(s).
Thanks for your help,
Jason
"Gary Chang[MSFT]" - 05 Aug 2005 03:12 GMT
Hi Jason,
>This problem is not recent. It goes back as far as I remember, at least
> to VS.NET 2002. I just checked and the same thing does occur with
>the Windows Forms Designer as well. The arrows keys have no effect
>on the selected item(s).
If so, have you tried a repairation/reinstallation of your VS.NET 2003?
If it doesn't work neither, this problem may be a product issue, in such
scenario it is better for you if one of our PSS support engineers could
work with you. This may need you submit a support incident in Microsoft PSS
(Product Support Service). As a MSDN subscriber, you have two free support
incidents.
By the way, if the problem is confirmed by Microsoft PSS as a product
issue, PSS won't charge money. Every MSDN subscriber has two free support
incidents. You could use one of them to contact Microsoft PSS. So you don't
need to pay money yet. Surely if the issue is a product issue, you still
have two free support incidents.
For your reference, I attached steps to contact Microsoft PSS here: You can
contact Microsoft Product Support directly to discuss additional support
options you may have available, by contacting us at 1-(800)936-5800 or by
choosing one of the options listed at:
http://support.microsoft.com/d-efault.aspx?scid=fh;EN-US;Offe-rProPhone
Thanks for your understanding!
Best regards,
Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn
This posting is provided "AS IS" with no warranties, and confers no rights.
Jason P - 05 Aug 2005 19:10 GMT
> If so, have you tried a repairation/reinstallation of your VS.NET 2003?
No, I haven't tried that, but I will.
> If it doesn't work neither, this problem may be a product issue, in such
> scenario it is better for you if one of our PSS support engineers could
> work with you.
Thanks for trying to help!
Regards,
Jason
"Gary Chang[MSFT]" - 06 Aug 2005 03:48 GMT
OK, Jason, thanks for your understanding on this issue.
Good Luck!
Best regards,
Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn
This posting is provided "AS IS" with no warranties, and confers no rights.
JimM - 04 Aug 2005 22:10 GMT
This has also happen on my system with VS.NET 2003. When I reboot the system
it seems to go away.
I have a feeling the Scroll Lock may be part of the problem. I use a KVM
and the key sequenct to switch system is Scroll Lock + Up or Down Arrow.
I really find this anoying when working on a form.

Signature
Jim
> Hi Jason,
>
[quoted text clipped - 26 lines]
>
> This posting is provided "AS IS" with no warranties, and confers no rights.