[AccessD] Dirty property
Susan Harkins
ssharkins at gmail.com
Thu Jul 23 18:36:18 CDT 2015
Got it. :) The button goes. I am glad for all the help. Thank you!
Susan H.
On Thu, Jul 23, 2015 at 5:20 PM, Steve Schapel <
steve at datamanagementsolutions.biz> wrote:
> Hi Susan
>
> Your conclusion is correct, but the rationale not quite right. I think
> you are assuming that the form's Close event is directly connected to the
> Close button in the form's Control Box. It's not. If that Close button is
> visible (which incidentally I never allow), and if it's clicked, there is a
> series of form events that are triggered. Probably AfterInsert in the case
> of a new record, followed by BeforeUpdate, AfterUpdate, Unload, and then
> Close. Don't quote me on the exact details ... but, you get the idea. So,
> the point is, that by the time the form's Close event comes around, the
> record has already been saved, and therefore that event is too late in the
> process to be testing for the value of the Dirty property - by that time it
> will always be False, not because you "cancel the current state of the
> form", but because the record has been saved and therefore it is not Dirty.
>
>
More information about the AccessD
mailing list