Enter key behavior

[Frank Reichenbacher]

In MS Access VB, which I have been using for several years, the default
enter key behavior in a textbox is identical to the tab key. Data are read
and the focus moves to the next control in the tab order. In VB.NET the
default behavior is that data are read, but the focus does not change. I
find this to be extremely bad form management. Users (including me) are
universally accustomed to using the enter key to move from one field to the
next in a wide variety of programs.

Is there some way to easily change this without constructing complex
keypress/validation code? I searched textbox properties and could find
nothing to switch.

Frank

 

[Cor Ligthert]

Frank,

The first thought I had was create your own inherrited textbox that has the
behaviour as you want and use those textboxes.

Cor

 

[Frank Reichenbacher]

Frank,

The first thought I had was create your own inherrited textbox that
has the behaviour as you want and use those textboxes.

Cor

Thank you for responding, Cor.


Note to Microsoft:

I don't need this particular headache, I have plenty of them already.
Nor can I afford the time it will take to figure out how to implement this
ridiculous and unnecessary workaround when code obviously already exists in
other MS programs to do it in a snap.

Frank

 

[Jeff Johnson [MVP:VB]]

Thank you for responding, Cor.


Note to Microsoft:

I don't need this particular headache, I have plenty of them already.
Nor can I afford the time it will take to figure out how to implement this
ridiculous and unnecessary workaround when code obviously already exists
in other MS programs to do it in a snap.

Why don't you add

--------
And while you're at it, please provide a property and/or method to do
every other little thing I could possibly need so I don't have to waste my
valuable time doing silly things like writing code.
--------

Welcome to programming. Access, Excel, et al. are very specific applications
with very specific functionality. VB (and C#, and C++, etc.) are
general-purpose programming languages. They can't be expected to do
everything under the sun automatically; rather the programmer is expected to
provide that functionality if it is necessary in a particular application.
For every request like yours to add functionality to the base
language/controls, someone else complains of feature bloat. You really have
no idea how many headaches you're ALREADY shielded from!

 

[Frank Reichenbacher]

Why don't you add

--------
And while you're at it, please provide a property and/or method to
do every other little thing I could possibly need so I don't have to
waste my valuable time doing silly things like writing code.
--------

Welcome to programming. Access, Excel, et al. are very specific
applications with very specific functionality. VB (and C#, and C++,
etc.) are general-purpose programming languages. They can't be
expected to do everything under the sun automatically; rather the
programmer is expected to provide that functionality if it is
necessary in a particular application. For every request like yours
to add functionality to the base language/controls, someone else
complains of feature bloat. You really have no idea how many
headaches you're ALREADY shielded from!

I think you missed my point. The default textbox behavior represents very
bad form management. It goes against enter key behavior which nearly all
users are accustomed to in a very wide variety of other applications,
Windows and non-Windows. I just loaded an old VB 4.0 package I found and I
note the behavior was in that package also. So it has survived all these
many versions unchanged.

Code bloat is first and foremost the result of marketing schemes not the
incorporation of necessary or desirable features.

Frank