>>Not sure if this the problem, but when you click on the keyboard form it is now the focus of input. So any keyboard input is now directed to this form and not the original form that you started with that has the textboxes or other input controls. I would think that you need to have a custom property at the _SCREEN or _VFP that retains the current input form (not the keyboard form). Use the Activate() event of the input form to assign it to the custom property; i.e. _SCREEN.InputForm = thisform. Each of the input controls can set a custom property in the form to give the current input control the user is entering into; use the GotFocus() or the When() events. I am not sure if the AciveControl property is reset when the form looses focus and then is again; if it is not reset, then you can use this to determine the current control for input.
>
>I think this is the main reason why the virtual keyboards go into a toolbar, because toolbar doesn't steal focus.

I used toolbar for keyboard control in first but toolbar doesn't seem smoothly for virtual keyboards, so I developed a picture button based virtual keyboard in a container control. I'll share my class...