Triggering Form On Dirty Event using VBA

[Guest]

In Access 2000, modifying data in a text box bound to a table with VBA code
would cause the forms "on dirty" event to fire.

I just ported an application from Access 2000 over to Access 2003 and have
discovered, to my dismay, that modifying data using VBA code causes the forms
"dirty" attribute to be set to true but it does not cause the forms "on
dirty" event to fire.

I have only been able to trigger the even by keying data myself; I even
tried using SENDKEYS in VBA to see if this would trigger the event but it
would not.

Has anyone found a fix for this lack of consistency between Access 2000 and
Access 2003? I hate to have to re-engineer my application that relies on vba
code modification of data to trigger the event.

Thanks

 

[Van T. Dinh]

See reply in "microsoft.public.access" newsgroup.

Please do not multi-post the same question. Most regular respondents read a
large number of newsgroups and do like to waste time reading the same
question.