Access 2007 form fields stuck on "New line in field"

[M Skabialka]

In Access 2007 I have created some forms and sub-forms for data entry. When
a user enters data in a data entry field and hits enter, they are given a
new line in the field instead of going to the next field. The only two
options on the field itself under 'Enter key behavior' are 'New line in
field' or 'Default'. When I change it to default and they hit enter,
nothing happens - they are left in the same position in the same field.
Most of the fields are text fields. I would like it to go to the next field,
as it used to in prior versions. Has something changed in Access 2007? How
can I fix this?

 

[Albert D. Kallal]

I never experienced your problem in 2007, it works for me like it always
did.

I would check if you removed the tab stop setting for the control. If none
on the controls have the "tab stop" property set to yes, then you will find
that tab (or enter) will NOT move to the next control. And, if there only
one control on the form with a tab stop you again not move anywhere.

Keep in mind, while the enter key can be set to go to the next field, since
windows 3.1 (17 years ago), the standard in windows (and now even web
browsers) has been to use the tab key to go to the next field.

The other thing to check is the "global" settings you have for the Enter
key.

office button-> Access options-> advanced

You see a section called

Move after enter
[ ] Don't Move
[x] Next Field
[ ] Next Record

The above settings also exist in access 2003 also. Perhaps you been messing
with the above settings as this can turn off enter key going to next
control.

The above setting is the first thing I would check.

 

[Maurice]

Changing it to default makes mine goto the next field. Try changing it again,
save the form - compact and repair and see if it works then...

 

[Fred]

One more thing to check. Is the field in question a memo field? It seems
to me that memo fields exhibit this behavior regardless of other settings.

 

[M Skabialka]

I never experienced your problem in 2007, it works for me like it always
did.

I would check if you removed the tab stop setting for the control. If none
on the controls have the "tab stop" property set to yes, then you will
find
that tab (or enter) will NOT move to the next control. And, if there only
one control on the form with a tab stop you again not move anywhere.

All tab stop properties are set to yes.

Keep in mind, while the enter key can be set to go to the next field,
since
windows 3.1 (17 years ago), the standard in windows (and now even web
browsers) has been to use the tab key to go to the next field.

But if I enter 2.1a or Standardization & Interoperability (S&I) in a field
and hit enter it should go to the next field, not just sit there. Tab does
work but that is not what people are used to.

The other thing to check is the "global" settings you have for the Enter
key.

office button-> Access options-> advanced

You see a section called

Move after enter
[ ] Don't Move
[x] Next Field
[ ] Next Record

This is what it was set at already.

The above settings also exist in access 2003 also. Perhaps you been
messing
with the above settings as this can turn off enter key going to next
control.

This is my first database created entirely with Access 2007, so there are no
remnants of 2003 in it.

The above setting is the first thing I would check.

I still have the problem. All fields are text, 255 char limit.
If I choose New line in field, I get a new line which I don't want. If I
choose Default, the curser doesn't move.

However in checking this out more, I have found it only happens in sub-forms
which are continuous forms. Subforms with only one record allow using enter
or tab to go to the next field. Parent forms that are not continuous are
OK, so I am guessing that continuous forms are the problem. I need a
solution!

Thanks,
Mich

 

[M Skabialka]

I have narrowed the problem down a little more. If I open the sub-form on
its own there is no problem. I set the enter key behavior to default and it
works, moving from field to field using either the tab or the enter key.
Then I re-open the main form and the sub-form no longer lets me use the
enter key to go to the next field. Nothing seems to be disabled or locked,
enabled is yes, etc on the form and sub-form.
Is there another setting for subforms I may be unaware of?
Mich

I never experienced your problem in 2007, it works for me like it always
did.

I would check if you removed the tab stop setting for the control. If
none
on the controls have the "tab stop" property set to yes, then you will
find
that tab (or enter) will NOT move to the next control. And, if there only
one control on the form with a tab stop you again not move anywhere.

All tab stop properties are set to yes.

Keep in mind, while the enter key can be set to go to the next field,
since
windows 3.1 (17 years ago), the standard in windows (and now even web
browsers) has been to use the tab key to go to the next field.

But if I enter 2.1a or Standardization & Interoperability (S&I) in a
field and hit enter it should go to the next field, not just sit there.
Tab does work but that is not what people are used to.

The other thing to check is the "global" settings you have for the Enter
key.

office button-> Access options-> advanced

You see a section called

Move after enter
[ ] Don't Move
[x] Next Field
[ ] Next Record

This is what it was set at already.

The above settings also exist in access 2003 also. Perhaps you been
messing
with the above settings as this can turn off enter key going to next
control.

This is my first database created entirely with Access 2007, so there are
no remnants of 2003 in it.

The above setting is the first thing I would check.

I still have the problem. All fields are text, 255 char limit.
If I choose New line in field, I get a new line which I don't want. If I
choose Default, the curser doesn't move.

However in checking this out more, I have found it only happens in
sub-forms which are continuous forms. Subforms with only one record allow
using enter or tab to go to the next field. Parent forms that are not
continuous are OK, so I am guessing that continuous forms are the problem.
I need a solution!

Thanks,
Mich

 

[M Skabialka]

More refinements to the problem:
All of the subforms have the problem (Enter does not go to the next field)
if they are inserted on one particular form, but not if they are inserted on
other forms.
What property of this form is stopping me from using Enter on the sub-forms?
I was going to recreate the form but the header has a background that fades
from left to right, and from top to bottom. I do not know how to transfer
this effect to a copy of the form. The boss likes it! The form properties
say there is an embedded image but doesn't show how to retrieve and re-use
it other than by copying the form and reusing it for the graphic effects.

I have narrowed the problem down a little more. If I open the sub-form on
its own there is no problem. I set the enter key behavior to default and
it works, moving from field to field using either the tab or the enter key.
Then I re-open the main form and the sub-form no longer lets me use the
enter key to go to the next field. Nothing seems to be disabled or locked,
enabled is yes, etc on the form and sub-form.
Is there another setting for subforms I may be unaware of?
Mich

I never experienced your problem in 2007, it works for me like it always
did.

I would check if you removed the tab stop setting for the control. If
none
on the controls have the "tab stop" property set to yes, then you will
find
that tab (or enter) will NOT move to the next control. And, if there
only
one control on the form with a tab stop you again not move anywhere.

All tab stop properties are set to yes.

Keep in mind, while the enter key can be set to go to the next field,
since
windows 3.1 (17 years ago), the standard in windows (and now even web
browsers) has been to use the tab key to go to the next field.

But if I enter 2.1a or Standardization & Interoperability (S&I) in a
field and hit enter it should go to the next field, not just sit there.
Tab does work but that is not what people are used to.

The other thing to check is the "global" settings you have for the Enter
key.

office button-> Access options-> advanced

You see a section called

Move after enter
[ ] Don't Move
[x] Next Field
[ ] Next Record

This is what it was set at already.

The above settings also exist in access 2003 also. Perhaps you been
messing
with the above settings as this can turn off enter key going to next
control.

This is my first database created entirely with Access 2007, so there are
no remnants of 2003 in it.

The above setting is the first thing I would check.

I still have the problem. All fields are text, 255 char limit.
If I choose New line in field, I get a new line which I don't want. If I
choose Default, the curser doesn't move.

However in checking this out more, I have found it only happens in
sub-forms which are continuous forms. Subforms with only one record
allow using enter or tab to go to the next field. Parent forms that are
not continuous are OK, so I am guessing that continuous forms are the
problem. I need a solution!

Thanks,
Mich

 

[Albert D. Kallal]

More refinements to the problem:
All of the subforms have the problem (Enter does not go to the next field)
if they are inserted on one particular form, but not if they are inserted
on other forms.

Ok, so then access is working fine here...except for this one form?

Does the enter key work fine on the main form part (non sub-form)?

I can't imagine you would do all this testing, but not check if the enter
key works on the main form part!

Perhaps you have a button control on the main form that has its default
property set to "yes". When you set a buttons "default" property to "yes"
(on the other tab of the property sheet) this setting means that ANYTIME you
hit the enter key on that form, the button will pressed. In other words,
this will hi-jack the enter key. note that if you set a buttons cancel
property = yes, then the button fires ANYTIME you hit the esc key. So, these
two properties of a button can hi-jack your key behaviors.

However, the above is likely a long shot on my part since you not mentioned
that the enter key don't work on the "main" form part, but only the sub
form? Anyway, check any and all buttons on that form...

header has a background that fades from left to right, and from top to
bottom. I do not know how to transfer this effect to a copy of the form.

Well, where did the form come from??? Forms often use a graphic set as a
background for the WHOLE form (in other words, in design mode, select the
form, and then check the format tab for a background graphic. (DO NOT select
the forms heading, but the whole form to find this background).

 

[M Skabialka]

The graphic turns out to be an Arrange - Autoformat feature - there is a
similar one I can choose from so that issue is covered.

The enter key works on other forms, and on these same subforms if they are
inserted into other forms.

BUT - you have (again) solved my problems. There was a button I am not even
using at the moment whose default was set to yes. As soon as I set it to no
everything started working properly. Never in a million years would I have
realized that that property could cause such a headache!

I was almost at the start over point - you have saved my sanity!
Thanks,
Mich