Harry-

> because it reads that as a change in the value of the property.
That's because it haschanged value! :)

Unfortunately, the _screen.activeform idea will have the same problem you are having now.

You could add a conditional breakpoint (in the breakpoint dialog window): TYPE('blah.blah') <> 'U' and deactivate the other breakpoint until the above breaks as true, then reactivate yours.