>Trey,
>
>Has my combobox issue become that obvious to the community? :-)
>

you know how it goes ;)

>Yes, it's the one and the same and it actually is a combobox. I was certain that there was no contained controls in a combobox, but when I saw it referenced in the Event Tracking it got me wondering... Perhaps it's just an internal Foxpro process that we don't see. This is what a relevant portion of the log looks like if you're curious:
>
>

>codes.t48_page_frame1.page3.cbo_code.KeyPress(9, 0)
>codes.t48_page_frame1.page3.cbo_temp_instance.When()
>codes.t48_page_frame1.page3.cbo_code.Valid()
>codes.t48_page_frame1.page3.cbo_code.LostFocus()
>codes.t48_page_frame1.page3.cbo_code.text1.LostFocus()
>codes.t48_page_frame1.page3.cbo_temp_instance.GotFocus()
>codes.t48_page_frame1.page3.cbo_temp_instance.Message()
>codes.t48_page_frame1.page3.cbo_temp_instance.text1.GotFocus()
>

>
>Renoir

Now that I've had the chance to run the event tracking, I see what you mean.
Makes sense, since the combobox is a compound control (hence the name, I guess). But we can't access the internal objects directly, so it's odd that it shows up in the event tracking log.