Dirty problem with numbers

[gg80]

I have a simple continuous form. Two text fields and one number (single format) field. When I close the form, I want a message to be generated if any field has been changed.

The code for the close button is:

If me.dirty then
msgbox "my message"
end if
docmd.close.



Weird event is that if text fields are changed, works fine. If change is made in number field, it doesn't sense the form as being dirty.

Anyone know what is going on? Happens in both access 2003 2007

[June7]

I tested your code and it works for me when editing a number type field. Can't replicate the issue. However, am testing with Access 2010 right now but expect would be same for 2007.

[orange]

You may get some ideas from this link. I read it based on another post recently.

http://www.access-programmers.co.uk/...d.php?t=210944

[Missinglinq]

This really needs to be done in the Form_BeforeUpdate event, not in the Form_Close event. Assuming that you only want this message to pop up if data on an existing Record has been changed, all you'd need would be:

Private Sub Form_BeforeUpdate(Cancel As Integer)
  If Not Me.NewRecord Then
    Msgbox "My Message"
  End If
End Sub

There's no need to check whether or not the Form has been Dirtied; if it hasn't been Dirtied, the Form_BeforeUpdate event won't fire!

Linq ;0)>

[gg80]

I tested your code and it works for me when editing a number type field. Can't replicate the issue. However, am testing with Access 2010 right now but expect would be same for 2007.

Thanks much. After your response, I recreated the source table and form in a new db file to see if some bug in old objects. I then opened and closed the new form about 50 times and changed the value in the number field on each opening. Now, it seems to work except that in about one in about 10-15 testing open-close cycles, it still doesn't sense dirty state when I change a number value. Maybe I should reload Access or at least run repair? Frustrating.

[Missinglinq]

What event are you using for the code at this time?

Linq ;0)>

[gg80]

[QUOTE=Missinglinq;158281]This really needs to be done in the Form_BeforeUpdate event, not in the Form_Close event. Assuming that you only want this message to pop up if data on an existing Record has been changed, all you'd need would be:

The form is a popup that allows the user to change some factors that could affect values on the main form. The message reminds him to take certain actions if he has made any changes. It is a more efffective message if it displays the reminder just as he closes the popup to go back to the main form. Plus, if he makes more than one change, the repeated message could be annoying.

[Missinglinq]

The Form_BeforeUpdate will only pop once, when the Record is saved, which occurs when the close the Form. I'd still try it in that event.

[gg80]

I checked it and, on my system (A2007), Form_BeforeUPdate (and Form_AfterUpdate) pop a message as soon as a change is made on any control.

[June7]

I also have now tested with A2007. The Form procedures trigger only when record is committed by closing form or moving to another record. I don't know what is going on with your form. If you want to provide db for analysis, follow instructions at bottom of my post.

[gg80]

Thanks for following through on this. The BeforeUpdate does respond as you described. But, moving to another record(s) on the form is just what will happen 50% of the time it is used, so a pop up on each move would be annoying. I want the message to fire only when the popup form is closed and only if a change had been made (me.dirty) to one or more of the fields.

[June7]

I am confused. I think that is the behavior I am getting. Can't replicate your issue. If you want to provide db for analysis, follow instructions at bottom of my post. However, I won't be able to work with it for two weeks starting tomorrow.