Okay, my problem is solved and easy as I always expected. So indeed the Zorder was wrong in this case (well, wrong ?) and had to put to back. But why ??

I can think of only one thing which is an exception to the other situations :

The shapes I create here are being creating while Event Reading is off, while the others do it with On (within Read Events). Now (I) note that the AddObject in this case will not fire some (internal ?) events which put the Zorder right and which for a shape normally is at the back (must be, because shapes never bother me).

Well, cheers,



>>>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:).
>
>--> What about a shape just covering the inside of the form ?
>
>> Their zorder(1) would do the trick at runtime if you didn't do it manually at design time (send to back).
>
>--> Manually I leave these things alone (except for special situations which are not applicable here).
>
>>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 :)
>
>--> Right. But here we (well I) don't talk about invisible (transparent) containes, but about visible shapes which -I learned- can mask objects in them too in my one situation. So again I wonder, what would - or can be special on this situation ? I really wouldn't know but for one thing : the shape covers the objects ... but they all do ! I mean, may others created in run-time, and many others created at desgin-time.
>Well, since we are talking about this anyway, I am going to find out right now.