>>>>I have a text box on a form that is enabled, and it's selectonentry is .t., but I can not click in the text box. I can tab into it and change the text as usual, but cannot click into it, even when I am already in the text box? The mouse cursor does not even change to an i-bar when I am over the text box. Does anyone have an idea of what my problem is here? Your help would be appreciated. Thanks
>>>
>>>Ross,
>>>There should be a transparent shape or container in front of it.
>>>Cetin
>>
>>100 % agreed. However, I put shapes around parts of my form all over the place (a sunken line as usual) and this never gives any problems. Remember, I do this afterwards (Objects in it are already there). But, I have this only one sutiation exactly as described, and didn't even begin to think on the reason;
>>
>>Cetin, what you describe, would this imply that shapes should always be drawn before the objects are there ? I mean the other way around : I think in my situation where it doesn't work the textboxes may be instantiated just after the shape is put there. On the other hand, all stuff created at design-time has shapes too, and they are obviously there before the objects (all being created at run-time). So ?? What's your opinion on this ?
>
>Peter,
>Before objects are there it'd be quite hard to determine how many shapes you need, where would they be (if you especially decide like me to put them afterwards:). Their zorder(1) would do the trick at runtime if you didn't do it manually at design time (send to back).
>It's generally hard to catch when a container covers partially a commandbutton. You click the button and it doesn't get it. You try again and it does :) If you only test once with a click to covered part you were likely ignore it thinking you couldn't click well( and end users would always click there I bet :)
>Cetin

My FoxSpeaker could be used for that. If FoxSpeaker is enabled, just click on suspicios part of the form and it will tell you what type of control is there.