It depends.
Say the form is positioned on record 'A' and the user is about to move to
record 'B'. Do you want your code to be executed while the form is still
positioned on record 'A' and before record 'B' becomes the current record?
In that case, you'll need to provide a custom navigation UI and disable the
built-in navigation methods. But if your code can be executed after record
'B' has become the current record, then you can use the form's Current
event.
--
Brendan Reynolds
Access MVP
"David" <(E-Mail Removed)> wrote in message
news:eCkq7sp$(E-Mail Removed)...
>I have some code that I would like to execute anytime that form changes to
>a different record without having to create my own navigation buttons. Is
>there anyway to do this?
>
|