>I'm begining to think we need a debugger category. :)
>
>Anyway, I've been hunting through the docs and am having no luck. What I need to do is set a breakpoint when the value of a textbox changes. The trouble is that it is buried deeply and I don't know the whole hierarchy to get to it. All I know is I want txtCode.value.
>
>I'll head off a few possible answers that don't work:
>
>1. I can't drag it from the locals window because there's so much stuff there that I can't find it.
>
>2. I can't go by when the control source changes because it's not changing and that's what the problem is.
>
>3. I can't insert the object reference in the code somewhere to see what it comes up with because SBT renames things at runtime, so I need to know what it's called then.
>
>4. I can't set anything in the code itself, because the purpose of this excercise is to find out where in the code it's changing.
>

If you don't mind navigating the _Screen's Forms collection, this might be useful:

In the main line for your application, issue the foillowing two lines:

PRIVATE oScreen =
oScreen = _SCREEN

oScreen refers to the same object as the system variable _SCREEN, will appear in the Locals Window, and you can dig through the collections/contained objects, etc as needed; you can set breakpoints on changes to your textbox content by drilling down to the appropriate control, etc.