>>>>The custom combo is too complicated to explain here, but it basically is a container with a textbox and some buttons. What is happening is that when it is tabbed into it takes two tabs to get to the next object on the form. Other than the textbox, the TabStop is .F. for the other objects inside the combo. Is it possible that the container itseff is accepting one of the tabs and then the textbox is getting the 2nd one? How can I make sure that the textbox gets the focus when the container/combo is tabbed into, and then leaves the combo/container when the next tab is pressed?
>>>>
>>>
>>>Set TabStop = .F. on skipped container's objects is sufficient.
>>
>>Actually, it's not. Those are already set to false. The first tab goes into the textbox, then the 2nd tab highlights the same textbox. I have code that is working now, but still having some issues checking for which parent.parent control to set focus to. Couple other threads regarding that.
>
>You have some code that corrupt the VFP standard behaviour.

Right. I said from the start it was a complicated custom combo. To explain all the little things involved would not be prudent, but if I could rule out some native behaviours, etc, then maybe I could narrow down the issue.