By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,647 Members | 1,604 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,647 IT Pros & Developers. It's quick & easy.

Access 2002: Form_Dirty does not fire

P: n/a
HJ
Hi all,

I notice that the Form_Dirty event does not fire in Access 2002 (SP-1) when
the first character is typed into a new record. In previous versions of
Access it does fire.

For existing records that are being edited, the event does fire.

Has this (previous) behaviour been changed by Microsoft?

HJ
Nov 13 '05 #1
Share this Question
Share on Google+
9 Replies


P: n/a
I'm not seeing this behavior in Access 2002 SP3.

Are you sure the record is not being dirtied programmatically?

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"HJ" <hj********@spamhotmail.com> wrote in message
news:41***********************@dreader16.news.xs4a ll.nl...
Hi all,

I notice that the Form_Dirty event does not fire in Access 2002 (SP-1)
when
the first character is typed into a new record. In previous versions of
Access it does fire.

For existing records that are being edited, the event does fire.

Has this (previous) behaviour been changed by Microsoft?

HJ

Nov 13 '05 #2

P: n/a
The OnDirty event only fires for bound controls, and bound forms. Also, if
VBA code makes any change to a bound form, it can prevent the Dirty event
from firing unless you specifically set Dirty to False after your code
executes.
Darryl Kerkeslager

"HJ" <hj********@spamhotmail.com> wrote:
I notice that the Form_Dirty event does not fire in Access 2002 (SP-1) when the first character is typed into a new record. In previous versions of
Access it does fire.

Nov 13 '05 #3

P: n/a
HJ
Hi,

Thanks for responding. The form is bound to a table and it is not being
dirtied programmatically; I am 'just' entering a new record. That means that
both the BeforeInsert and the Dirty event should fire. The BeforeInsert
event does fire, the Dirty one does not.

I have now also seen this behaviour on another form that does not have a
BeforeInsert event. Here too the Dirty event does not get fired.

Still, this only happens in Access 2002. In Access 2000 the Dirty event gets
fired all the time (and I like that!).

HJ

"Darryl Kerkeslager" <Ke*********@comcast.net> wrote in message
news:B8********************@comcast.com...
The OnDirty event only fires for bound controls, and bound forms. Also, if VBA code makes any change to a bound form, it can prevent the Dirty event
from firing unless you specifically set Dirty to False after your code
executes.
Darryl Kerkeslager

"HJ" <hj********@spamhotmail.com> wrote:
I notice that the Form_Dirty event does not fire in Access 2002 (SP-1)

when
the first character is typed into a new record. In previous versions of
Access it does fire.


Nov 13 '05 #4

P: n/a
I have not seen this behavior (Thankfully). I use A2002, but save my mdb as
A2000 for compatibility. Perhaps that is the difference.
Darryl Kerkeslager

"HJ" <hj********@spamhotmail.com> wrote:
Still, this only happens in Access 2002. In Access 2000 the Dirty event gets fired all the time (and I like that!).

Nov 13 '05 #5

P: n/a
HJ
Nope, same here. I am quite stumped. The workaround is, of course, to call
the Dirty event from the BeforeInsert event, but that does not really solve
the initial problem.

HJ

"Darryl Kerkeslager" <Ke*********@comcast.net> wrote in message
news:FL********************@comcast.com...
I have not seen this behavior (Thankfully). I use A2002, but save my mdb as A2000 for compatibility. Perhaps that is the difference.

Nov 13 '05 #6

P: n/a
"Darryl Kerkeslager" <Ke*********@comcast.net> wrote in
news:FL********************@comcast.com:
I have not seen this behavior (Thankfully). I use A2002, but save
my mdb as A2000 for compatibility. Perhaps that is the
difference.


The "dirty event" exists only *after* A2K, no (as opposed to the
"dirty property/method")?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #7

P: n/a
Darryl Kerkeslager wrote:
The OnDirty event only fires for bound controls, and bound forms. Also, if
VBA code makes any change to a bound form, it can prevent the Dirty event
from firing unless you specifically set Dirty to False after your code
executes.


Setting Dirty to false will force a save of the record, not good if
you're just starting out and there are required fields not yet entered.

--
This sig left intentionally blank
Nov 13 '05 #8

P: n/a
"David W. Fenton" <dX********@bway.net.invalid> wrote in message
news:Xn**********************************@24.168.1 28.78...
"Darryl Kerkeslager" <Ke*********@comcast.net> wrote in
news:FL********************@comcast.com:
I have not seen this behavior (Thankfully). I use A2002, but save
my mdb as A2000 for compatibility. Perhaps that is the
difference.


The "dirty event" exists only *after* A2K, no (as opposed to the
"dirty property/method")?


It's on Microsoft's "What's New" page for Access 2000.

http://msdn.microsoft.com/library/de...a2000intro.asp

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 13 '05 #9

P: n/a
True. I usually fill all required fields in first by code, or set a default
value.

Darryl Kerkeslager

"Trevor Best" <no****@besty.org.uk> wrote:
Darryl Kerkeslager wrote:
The OnDirty event only fires for bound controls, and bound forms. Also, if VBA code makes any change to a bound form, it can prevent the Dirty event from firing unless you specifically set Dirty to False after your code
executes.


Setting Dirty to false will force a save of the record, not good if
you're just starting out and there are required fields not yet entered.

Nov 13 '05 #10

This discussion thread is closed

Replies have been disabled for this discussion.