[AccessD] Dirty property

[Susan Harkins]

Well I don't mean to start anything, but I an willing to learn. What I
think you're saying is... Access assumes when you click the Close button
that you want to cancel the current state of the form... and thus... the
Dirty property will also be False. If this is correct, I know how to
proceed and I'm glad for the discussion. :) I'm just going to disable the
Close button. :)

Susan H.

On Wed, Jul 22, 2015 at 7:46 PM, Darryl Collins <
darryl at whittleconsulting.com.au> wrote:

> This is why you want to use unbound controls, as they behave as the user
> would expect - not as the database does.  When a user 'cancels' a form they
> expect the record to be dropped.  This is not the case when using a bound
> form.
>
> Naturally this topic (bound/unbound) often ignites a firefight - so sorry
> for bringing it up, but that is my experience and one of the many reasons I
> use unbound forms.
>
> Cheers
> Darryl.
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Susan Harkins
> Sent: Thursday, 23 July 2015 8:52 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Dirty property
>
> 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.
>
>