Probably.  Trap what and when?

No. And there shouldn't be a reason for that. There are plenty of
events in an Access form that you can do anything you need without it.
Form_Current is probably the closest; it fires any time the user has
moved to another record.
What are you having difficulty with?

-Tom.

No.  But you could create your own.  I do this on lots of my applications,
when I want more control over the appearance and use of the controls that the
generic navigation buttons provide.

I think Allen Browne (www.allenbrowne.com) has code for a navigation control
subform that you could use as a start point for what you are doing.

Dale

Depends on what you *really* mean.  Do you mean "when they use the navigation
buttons" or do you mean "when they navigate"?  I ask because there are numerous
ways a user can change to a different record (navigate) without actually using
the buttons.

If you only need to know when they specifically use the buttons then the best
thing to do is remove the display of the built in ones and substitute your own
as others have suggested.

If you need to know any time they change records regardless of the means they
use to do so, then you need to use the Current event of the form.  Of course
that fires "as you arrive at a record", not "as you are leaving a record".  If
you need the latter then you have a dilemma as there is no simple way to do
that.