Event form_dirty not occurs

Hi,

I have a form, that is bounded to a table and had form_dirty event
procedure.
But this event doesn't occur at all. Why?
I have checked the property window, Datasource property and event Dirty, all
is OK.

thanks for help
Nhan

"Nhan" wrote in message

Hi,

I have a form, that is bounded to a table and had form_dirty event
procedure.
But this event doesn't occur at all. Why?
I have checked the property window, Datasource property and event
Dirty, all is OK.

thanks for help
Nhan

The Dirty event won't fire if you have dirtied the form with code, even
if now the form is modified by user action. Could this be the problem?

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

even if now the form is modified by user action
What do you mean? Macros? Not by macros

Could this be the problem?
The Form is not changed by code, but by keyboard

I am surprised, that an article in MSDN demonstrates, how we can check and
reag dirty property of a form. Why? Does it mean, that we should not use
Form_dirty event?

ACC2000: How to Automatically Detect If a Form Is Being Edited
Q210334

Method 2: Using the Dirty Property in an Expression
1.. Follow steps 1 through 4 in Method 1.


2.. Add a new text box with the following properties to the form:



Name: txtEditModeChange
ControlSource: =[Form].[Dirty] & EditModeChange([Form])
Visible: No 3.. On the View menu, click Code.


4.. Create the following function in the module, and then close the
module:



Function EditModeChange (F As Form) As Variant

If F.Dirty Then
F!btnUndo.Enabled = True
Else
F!btnUndo.Enabled = False
End If

End Function 5.. Set the form's AfterUpdate property to the following event
procedu



Sub Form_AfterUpdate ()
Me!txtEditModeChange.Requery
End Sub

"Nhan" wrote in message

even if now the form is modified by user action
What do you mean? Macros? Not by macros

Could this be the problem?
The Form is not changed by code, but by keyboard

Hmm. If the value of a bound control is modified by user action, and
the form is not already dirty, then the Dirty event should fire. If
that's not happening in your case, something peculiar is going on.

I am surprised, that an article in MSDN demonstrates, how we can
check and reag dirty property of a form. Why? Does it mean, that we
should not use Form_dirty event?

ACC2000: How to Automatically Detect If a Form Is Being Edited
Q210334

The Dirty event and the Dirty property aren't quite the same. The Dirty
property is True whenever the form's record has been modified but not
yet saved, no matter how that modification occurred. The Dirty *event*
fires only when a user action (via the user interface) causes the form
to become dirty or when the Text property of a bound control is changed,
when it wasn't dirty before.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

again,
this form worked well, then I changed some code, now the dirty event is not
fired. When I let the recordselector visible, I can see that the record is
changed, when I type a character in a textbox, although dirty event is not
fired.

"Dirk Goldgar" schrieb im Newsbeitrag
...
"Nhan" wrote in message

Hi,

I have a form, that is bounded to a table and had form_dirty event
procedure.
But this event doesn't occur at all. Why?
I have checked the property window, Datasource property and event
Dirty, all is OK.

thanks for help
Nhan

The Dirty event won't fire if you have dirtied the form with code, even
if now the form is modified by user action. Could this be the problem?

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

"Nhan" wrote in message

again,
this form worked well, then I changed some code, now the dirty event
is not fired. When I let the recordselector visible, I can see that
the record is changed, when I type a character in a textbox, although
dirty event is not fired.

The obvious question is, what code did you change?

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

again,
this form worked well, then I changed some code, now the dirty event
is not fired. When I let the recordselector visible, I can see that
the record is changed, when I type a character in a textbox, although
dirty event is not fired.

The obvious question is, what code did you change?
I have changed and add a lot of code and functions, I can't tell you, what.
But the basic function to deactivate and activate buttons, when form is
dirty, is not changed.

In old version, the dirty event is also fired, when a textbox is set to new
value over VB code.
The scenario:
- on a form there is a combobox for articles, when users type a new value
and choose it , notinlist event is fired.
- then the form article will be opened, and the new value from combox will
be filled in the article name Textbox. Now the Dirty event is fired, that
is, what I desire.

Have you checked that the "On Dirty" row of the Form's Properties still have
"[Event Procedure]" in the row?

If it has, put a Break on the Sub declaration and trace it. Make sure you
compile the code first in case there is a Compile error somewhere else that
can affect the entire code.

--
HTH
Van T. Dinh
MVP (Access)


"Nhan" wrote in message
...
I have changed and add a lot of code and functions, I can't tell you,
what.
But the basic function to deactivate and activate buttons, when form is
dirty, is not changed.

In old version, the dirty event is also fired, when a textbox is set to
new
value over VB code.
The scenario:
- on a form there is a combobox for articles, when users type a new value
and choose it , notinlist event is fired.
- then the form article will be opened, and the new value from combox will
be filled in the article name Textbox. Now the Dirty event is fired, that
is, what I desire.

"Nhan" wrote in message


In old version, the dirty event is also fired, when a textbox is set
to new value over VB code.

That should *not* have happened, unless the old code set the text box's
Text property, rather than its Value property. Setting a control's
Value property in code does not raise the form's Dirty event, but
setting its Text property does -- if the form is not yet dirty, that is.

The scenario:
- on a form there is a combobox for articles, when users type a new
value and choose it , notinlist event is fired.
- then the form article will be opened, and the new value from combox
will be filled in the article name Textbox. Now the Dirty event is
fired, that is, what I desire.

If your code is currently like this:

DoCmd.OpenForm "Article"
Forms!Article!ArticleName = Me!cboArticle

Try changing it to be like this:

DoCmd.OpenForm "Article"
With Forms!Article!ArticleName
.SetFocus
.Text = Me!cboArticle
End With

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

"Van T. Dinh" schrieb im
Newsbeitrag ...
Have you checked that the "On Dirty" row of the Form's Properties still
have
"[Event Procedure]" in the row?
Yes

If it has, put a Break on the Sub declaration and trace it. Make sure you
compile the code first in case there is a Compile error somewhere else
that
can affect the entire code.

I have done, therefore I knew, that the event is not fired