me.dirty doesn't seem to fire

[PeterW]

I am using the me.dirty property of a form to enable a save button to
highlight changes have been made. This seems to work fine except on the first
record shown by the form. When the form is opened at the first record any
change will make the button enabled and this will continue to work until I
update a field using a calendar control. After this the button appears
disabled and any alteration to the form doesn't seem to trigger the event
again. If I move to any other record all works fine
Anybody any ideas?

 

[Stefan Hoffmann]

hi Peter,

I am using the me.dirty property of a form to enable a save button to
highlight changes have been made.

You may also query Me.NewRecord.


mfG
--> stefan <--

 

[Allen Browne]

Peter, you are using the form's Dirty event procedure to enable your button?
(The form's Dirty property is a yes/no value.)

At least in some versions of Access, the Dirty event doesn't fire if the
record is dirtied programmatically. Therefore I would assume that whatever
is happening with your calendar control, it is dirtying the record, so the
Dirty event doesn't fire, so the button doesn't get enabled.

If that's the case, the solution will involve tracking down why the record
is being dirtied unnecessarily, and fixing that problem.

 

[PeterW]

Thanks for your help - what is confusing me is that this only happens with
the first record in the set - if I move to another record then everything
works fine