>Terry,
>
>>Sometimes I need to "idle" a focus away from a control, I use a little-bitty tansparent (not invisible) textbox control that I hide behind some other control on the form. When I need to loose the focus - I setfocus to the tiny textbox.
>
>I use the same technique only I place my textbox offscreen where it can never be seen, i.e. This.Move( -1000, -1000 )
>
>Two problems with this technique:
>
>1. I don't want the current control to lose focus causing premature validation

I seem to be on/off tracking this thread (trying to skip its other branches which used to pop up), so I don't know exactly where we stand at the moment. So forgive me if this was already mentioned:

When the user types into a control which is partially hidden by your container... are they supposed to go typing under it? If the container is partly transparent... then this is just a bit ugly, but not unusable.

I'm on this because three years ago, in VFP7, I had a problem with a textbox which would occasionally bleed through a container, or (worse) show once more in its original position after the form was resized. Now knowing what was the cause, I should have used the SetFocusToDummyTextbox thingy (which actually existed in the framework - VFE) so I'd have no active control during the resize. I'm now two jobs after that, but I'm still curious how this will be solved.

>>That Dragan - where would the digital rights cause of everyday form controls be without Dragan's advocations!:-)
>
>LOL!

:)

But then, someone has to stand up for these poor bleeding textboxes... we don't want them to lose too much digital blood, do we?