>Harry-
>
>> because it reads that as a change in the value of the property.

>That's because it haschanged value! :)

only in the sense of now being out of scope and thus not reportable...

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

now, I found that it worked in the sense that it constantly displayed the correct value but that setting a breakpoint on it seemed to cause all sorts of weird behaviour. The original need for the solution then promptly fixed itself so I haven't tried to sort it out past that point yet...

>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.

I tried that at the time and it breaks just as often, presumably because the object 'type' goes in or out of scope at the same time as any other property of the object.

Harry