> Hello Everyone, I am scratching my head over this one and am hoping you
> may
[quoted text clipped - 18 lines]
>
> End Sub
The Dirty event isn't really appropriate for this, from your description.
The Dirty event only fires when a record is modified, so merely paging from
record to record won't fire it. I think you should probably be using the
Current event.

Signature
Dirk Goldgar, MS Access MVP
www.datagnostics.com
(please reply to the newsgroup)
NeonSky - 21 Mar 2008 15:49 GMT
Hello Dirk, Thank you for you response! Though when I change "Dirty" to
"Current", I receive the following error message "Procedure declaration does
not match description of event or procedure having the same name." Any
thoughts? Thanks!
>> Hello Everyone, I am scratching my head over this one and am hoping you
>> may
[quoted text clipped - 6 lines]
>record to record won't fire it. I think you should probably be using the
>Current event.
Dirk Goldgar - 21 Mar 2008 19:24 GMT
> Hello Dirk, Thank you for you response! Though when I change "Dirty" to
> "Current", I receive the following error message "Procedure declaration
> does
> not match description of event or procedure having the same name." Any
> thoughts?
The event procedure for the Dirty event has a Cancel argument, while the
event procedure for the Current event does not (because the Current event
can't be cancelled). Change the proc header that I presume you have now:
Private Sub Form_Current(Cancel As Integer)
to this:
Private Sub Form_Current()
That ought to fix it.

Signature
Dirk Goldgar, MS Access MVP
www.datagnostics.com
(please reply to the newsgroup)