I have recently converted an Access 2000 database to Access 2007 and I
am now having problems switching between edited records. DB has
multiple forms and all now have the following behaviour.

Problem (Continuous form):
Edit data in a field of an exiting record.
Try to click into to the next record and the cursor will not move from
the field previously being edited.

Work-around:
Edit field, click into another field of the SAME record (previous
field change accepted).
Press Esc and now you can change to the next record (previously edited
record is retained including edited field).

Related Issue (Single form with sub form):
Edit data in an existing field, click into a subform - cursor will not
leave field being editied.

Work-around:
Edit field, click into another field on the same form (cursor moves to
new field and previous edit accepted).
Press Esc, click into subform (Cursor now moves into subform - edited
data on main form is retained).

While these work-arounds work they are a pain - slow and frustrating
and are contrary to normal behaviour.

If no edit has been done there is no problem switching between
records.
The original Access 2000 version still works normally - you can move
between edited records and between the main form and sub forms,
without having to press Esc inbetween. If you do press Esc the edits
are undone as one would expect. The forms are the same in the 2007
version, although the layout has been moved around a little.

Can anyone offer any suggestions why the 2007 version is working as it
is? (before I go around the bend!!)

Allan

"alches" <alches (AT) iinet (DOT) net.au> wrote


I'm not aware of a particular change in this behavior by design.

I would perhaps check the record cycle settings for the form in the other in
the property sheet.

Another possibility is the tab order or tab stop for that particular control
been changed to "no".

As mentioned, I don't see any other posters experiencing this problem. So
something's been changed here. Perhaps is there some type of code running
and security is preventing the code from running? Try setting your macros
security to low, and see if that changes anything, also check the forms
cycle properties, and also the tab stop issue setting.

So, I can only say this is not normal behavior, and something is definitely
wrong here.


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal (AT) msn (DOT) com

Hi Albert,

Thanks for your reply.

I had previously checked the record cycling and that is set to All
Records on every form, as it is on the original 2000 version.

There were no fields in the 2000 version that had the tab stop set to
No, so I changed the couple that had been set to Yes in 2007 version
back to No, but still have the same problem. I did not think that
would be the issue, as it still won't move records (without the Esc
inbetween) even if you mouse click into the next record.

There is no unusual code running - the forms are very basic, display
the records and a couple of buttons off to other forms, thats about
it.

I must admit that the 2007 'Ribbon' has me confused. I used to know
where everything was previously, now I am searching all the time.
Where do I find the 'global' settings, such as startup form, icon to
use, whether toolbars are active, whether certain keystrokes are
allowed etc.?
Do you know of any global setting anywhere that may affect this
behaviour?

Allan

"alches" <alches (AT) iinet (DOT) net.au> wrote


the old way, was tools->options.

new, is office button (pizzia), and then lower right, we have access
options.

Now, you have on the left nav you see current database etc. Perhaps enter
key behavior (as opposed to using tab for example), is the issue here? ).
So, check out "client settings" in the above options settings. There is
settings for the enter key behaviors etc.

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal (AT) msn (DOT) com