G
Guest
I have many date controls on different forms in different Access 2007 projects.
At least 2 of them have afterupdate events and it seems as if Access now
triggers an afterupdate event when the date control is entered/receives
focus. If you examine the date in the event sub you find that the oldvalue
and value properties are identical.
I can write code to get around this problem but I think this is an access
bug associated with date picker. I'm pretty sure there is another bug
associated with the date picker too, but a previous post regarding that fault
did not get any replies.
Has anyone else seen this behaviour? Is there a reason for it? Its a pain to
have to go through all my Access projects looking for situations where there
might be problems with what I suspect is an erroneous trigger of the
afterupdate event.
At least 2 of them have afterupdate events and it seems as if Access now
triggers an afterupdate event when the date control is entered/receives
focus. If you examine the date in the event sub you find that the oldvalue
and value properties are identical.
I can write code to get around this problem but I think this is an access
bug associated with date picker. I'm pretty sure there is another bug
associated with the date picker too, but a previous post regarding that fault
did not get any replies.
Has anyone else seen this behaviour? Is there a reason for it? Its a pain to
have to go through all my Access projects looking for situations where there
might be problems with what I suspect is an erroneous trigger of the
afterupdate event.