>What I was thinking of was using a couple of OKLs to extend your development environment. If you press Ctrl-Alt-F12 (pick a key you like), you fire a routine that saves WONTOP() to a public and starts your code to watch the mouse and read AMOUSEOBJ(). Mouse around until you find what you're looking for (you might start up a form with a timer that reads AMOUSEOBJ() and displays what you're positioned on in a wait window box or whatever - it's your little tool!)
>
>When you're whereever you want to be, press a different key that reads the information about the form/control your mouse is over using AMOUSEOBJ(), and pops up a form with the information you need. Put a command button in the form that shuts down (or hides) the form, and ACTIVATE WINDOW the value saved when you pressed Ctrl-Alt-F12, taking you back to what you were doing...
>
>>Ben

Ed,

The idea sounds good. But I wonder if I understand the whole picture. I see the following complications:

1. When there are more than 1 objects with the same name on the form. The information we got from AMOUSEOBJ() may not be enough for determining which is the corresponding object
2. Sometimes the form may be covered by another form. Or the corresponding object may be in a page, which is not currently on the top of a pageframe.

Ben