M MarkA70 Registered User. Local time Today, 15:06 Joined Jan 30, 2016 Messages 43 Mar 30, 2016 #1 What would cause the On Dirty event not to fire on a form. The form does not have data being entered programatically.
What would cause the On Dirty event not to fire on a form. The form does not have data being entered programatically.
arnelgp ..forever waiting... waiting for jellybean! Local time Tomorrow, 04:06 Joined May 7, 2009 Messages 20,380 Mar 30, 2016 #2 it will not fire if you did not change/add anything on any control on the form.
pbaldy Wino Moderator Staff member Local time Today, 13:06 Joined Aug 30, 2003 Messages 36,272 Mar 30, 2016 #3 I don't think it fires on unbound forms either.
missinglinq AWF VIP Local time Today, 16:06 Joined Jun 20, 2003 Messages 6,420 Mar 30, 2016 #4 Nor will it fire if one or more Controls have a Default Value. Perhaps a little more explanation of what's going on, here, would help us help you! Linq ;0)>
Nor will it fire if one or more Controls have a Default Value. Perhaps a little more explanation of what's going on, here, would help us help you! Linq ;0)>
pbaldy Wino Moderator Staff member Local time Today, 13:06 Joined Aug 30, 2003 Messages 36,272 Mar 30, 2016 #5 missinglinq said: Nor will it fire if one or more Controls have a Default Value. [/B] Click to expand... It should still fire when a control is changed by the user. Did in a brief test, with a bound form and a control with a default value.
missinglinq said: Nor will it fire if one or more Controls have a Default Value. [/B] Click to expand... It should still fire when a control is changed by the user. Did in a brief test, with a bound form and a control with a default value.
missinglinq AWF VIP Local time Today, 16:06 Joined Jun 20, 2003 Messages 6,420 Apr 1, 2016 #6 Of course it will! It'll fire (maybe I should say 'should fire') anytime data in entered into Control or existing data is edited. But simply because a Default Value 'appears' in a New Record doesn't mean that, in fact, a New Record has been created!
Of course it will! It'll fire (maybe I should say 'should fire') anytime data in entered into Control or existing data is edited. But simply because a Default Value 'appears' in a New Record doesn't mean that, in fact, a New Record has been created!