Yes, I have read those and other stuff on resizing. To answer Jeff Butler's question, my basis is "everything is relative," hence the reference to the additional control properties. Not that I would necessarily resize a command button, but based on the new size of the form, I could reposition any command button based on the the new height and width of the form as compared to the form's original dimensions and the original top and left coordinates of the button. Regardless of where the resizing occurs, form-level or control-level, resizing and repositioning must be in terms of relativity or an original reference point. I just think this would make better sense, and be easier, to have this at the control level.

>That makes too much sense, Mark :-D
>
>Have you looked at the articles on resizing in FoxPro Advisor?
>
>
>>... controls [e.g., command buttons, textboxes, etc.] have Resize methods? Even adding a resize method to my subclass of such controls does not automatically fire if I resize a form. :( So much for encapsulating all code within these classes.
>>
>>I guess what I am looking for are opinions and thought on what would be the best way to handle this while thinking outside the box [i.e., regardless of how we currently have to handle this].
>>
>>My thought would be that each control have its own resize method and a few more properties to store the original parent container's dimensions, the control's original dimensions and coordinates [top, left]. From there, everything is now relative, the control does not have to be resized or repositioned by some parent's resize method.
>>
>>Just wondering.