>>>Those functions will not work with VFP native textbox or editbox controls. Because, you will have to obtain the hWnd of the textbox or the editbox which VFP hides.
>>
>>VFP doesn't hide them, those controls don't have them because they are not "Windows" controls, they are only bitmapped representations to appear to look like standard Windows controls.
>
>Fred,
>
>Thanks for clarifying that!
>
>Fascinating!!!
>
>Could you explain in more detail how it's done internally?
>How are the controls rendered on the form?
>Why did VFP Team choose to use windowless controls?
>When you say those controls, do you mean TextBox and EditBoxControl or all the visual controls?
>
>And how did you know this?( Special connection with VFPT?:) )

No, no special connection with the VFPT, other than previous betas. It's been fairly well know for a few years that they're not Windows controls with handles.

The reason they did it, was for when there was a Mac version of VFP, so that there could be platform independence. Why it remains that way now, since there's been no Mac version (or Linux, or other) since VFP3, I have no idea. I have no idea how things are rendered inside VFP, though it wouldn't surprise me if GDI+ comes into play now more than ever.