Re: Dirty property not changing?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Reggie (NoSpam_webmaster_at_NoSpam_smittysinet.com)
Date: 08/03/04 

Date: Mon, 2 Aug 2004 22:40:05 -0700

grep, that is true. a calculated control is not bound to the record so
therefore changing its value does not put the record in a dirty state of
mind;-). If however, changes to bound controls of the record are what is
changing your calculated controls value, then this will place the record in
the dirty state. Moving focus to a control outside of the current record,
like a button in your header, or to a different record, will cause access to
save the record automatically. Hope this helps! 

-- 
Reggie
----------
"grep" <d0ughb0y35@netzoola.net> wrote in message
news:Om2MK2NeEHA.1644@tk2msftngp13.phx.gbl...
> Hey - while on the subject, what makes the dirty condition kick? Is it
> only when data has been modified? I've had calculated fields which have
> changed because of changes to their components, but this doesn't seem to
> kick the Dirty event.
>
> Arvin Meyer wrote:
> >
> > The record has already been saved by the time the Unload event occurs.
If
> > you are trying to trap a condition before the Dirty condition becomes
false,
> > use the Form's BeforeUpdate event.
Quantcast