[AccessD] Dirty property

Susan Harkins ssharkins at gmail.com
Wed Jul 22 17:51:43 CDT 2015


So, usurping the form's Close event doesn't keep it from saving -- that's
confusing to me. What am I missing? Why would the Close button save the
record? I expect it to prompt me, not automatically save.

Susan H.

On Wed, Jul 22, 2015 at 6:23 PM, Steve Schapel <
steve at datamanagementsolutions.biz> wrote:

> Well, if you are testing for the value of the Dirty property, the new
> record will have already been saved/committed by the time you get to the
> form's Close event, so yes, I would expect it to be False at that point.
>
> Regards
> Steve
>
> -----Original Message----- From: Susan Harkins
> Sent: Thursday, July 23, 2015 9:54 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Dirty property
>
>
>> Both, but specifically in this case, I'm talking about the Close button at
>> the top-right of the form. It seems easier to just remove those. :)
>>
>>
> Susan H.
>
>
>> "The code behind that event uses Me.Dirty to check for any new values."
>>
>> What event are you referring to?  Do you have a command button on the
>> form, and you are looking at the Click event of the button?  Or do you
>> mean
>> the form's built-in [x] close button, and you are looking at the form's
>> Close event?  Or something else?
>>
>> Regards
>> Steve
>>
>>
>>  --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


More information about the AccessD mailing list