events for record navigator

M

mcnews

are there no events associated with the record navigator?
such as previous_click, next_click, first_click, last_click,
newrec_click or something?
 
M

mcnews

Certainly.

create a button in the wizard and select 'record navigation'.
Click to expand...

i'm talking about the MS Access form record Navigation Buttons - not a
button that i draw.
 
M

Mark

The form's Current event fires any time the form goes to a different record.
The navigation buttons move the form to a different record so the form's
Current event fires when you click any of the navigation buttons.

Steve
 
M

mcnews

The form's Current event fires any time the form goes to a different record.
The navigation buttons move the form to a different record so the form's
Current event fires when you click any of the navigation buttons.

Steve
Click to expand...

so you're saying the answer to my question is no?
 
M

Mark

Strictly speaking, there are no properties associated with the navigtion
button's where you can assign code to an event. However you can get code to
execute when you click any of the navigation buttons by putting the code in
the form's Current event.

Steve
 
M

mcnews

Strictly speaking, there are no properties associated with the navigtion
button's where you can assign code to an event. However you can get code to
execute when you click any of the navigation buttons by putting the code in
the form's Current event.

Steve
Click to expand...

i am trying to not use the on current event.
something is going on in my app this is causing the on current event
on my subform to fire more than 3 times every time i move the main
form to a new record.
i have spent several hours trying to trace what might be causing this,
but have failed so far.

so i know all about the on current event - except how to stop it.
 
M

Mark

One of 3 things is happening since the Current event in the main form is
causing the current event in the subform to fire multiple times ---
1. When the main form goes to a new record, it goes to one or more other
records first
2. When the main form goes to a new record, it causes the subform to go
to one or more other records before going to a new record
3. Code in the subform's Current event causes the main form to jump to a
new record.

Steve
 
Top