The right values show in the activate. Now I can deal with it. I thought I had tried the activate clause.

I have a good clean set of wrapper classes for my Active X's. I drop container objects on my forms the containers deal with the Active X's. The only problems is DBI's pak has 54 controls. I have some editor macros that allow me to easily deal with building the methods at design time. All the events in the active X controls are back hooked into methods in the container. I have 13 controls wrapped with anywhere from 60 % - 90 % of the functionality dealt with in each control. It is very tedious.

The whole thing works great and looks and feels like commercial quality non foxpro based software except when I drop an object on top of the tab instead of in the tab. Thanks for the help.

>Ron,
>
>I only used Click() because it's a handy place to trigger code for example purposes. You can probably use a form level boolean lFirstActivate, set it to .t. and in the Activate:
>
>

if ( this.lFirstActivate )
>   this.lFirstActivate = .f.
>   * do more position related junk here
>endif

>
>ActiveX controls are working in their own HWND window on top of your form, you will not be able to put a VFP form object over the top of them.
>
>>Your right. I was under the impression that all positions of objects on a form had been calculated and had been set by the init of the form. Not having to worry about it has, it has not been a problem.
>>
>>I now see that is not true. I am working on a methodology with a DBI active X List Bar on the left. All forms obviously work to the space left over on the right. At runtime most forms turn off the title bar, set their background color to the screen background color and maximize/center themselves to the space left over no matter the screen resolution. All of my activex X controls are run inside of containers. With the LISAG rule in mind as well as this example where would you do these re-adjustments before the screen becomes visible. They are still not set by G-GotFocus.
>>
>>I guess I could set visible to .T. in the click event. Without having tried it would think the click event would not hit if the the form was not visible. I will try.
>>
>>If that is true then under certain conditions the load path is LISGAC. :)