>>>>Put a grid anchor=15.
>>>>
>>>>after run form. change grid's left property as a bigger value.
>>>>
>>>>resize form. Grid's left property resetting the first initial... :(
>>>>
>>>>There will no VFP10 and probably no patch... :(
>>>
>>>Setting anchor to a non-0 value has interesting (but documented) consequences for moving things. In many situations, you need to store the anchor value, move the object, then reset the anchor.
>>>
>>>Tamar
>>
>>Hey! It works!!! Thank you!.. Great!!! I tried reset left propery from resize method with no success. Your workaround excellent...
>>
>>Update: You right. If I would be look for anchor to help I would be see:
>>
>>Anchoring is based on the coordinates of the control at the time when the control's Anchor property is originally set, typically, when the control is instantiated. It is not based on the control's current position. Therefore, even after you move a control, anchoring applies to the control's original position. This behavior explains the difference between an Anchor value of 0 and 3.
>
>Yep. I spent a lot of time struggling with anchoring for an app. It's great when it works, but in this app, I was building a highly graphical form at runtime, and the user could drag and drop. The spec was that resizing the form should change the size of everything on the form (including increasing or decreasing font size). Took a lot of work to get it right.
>
>Tamar

I used my xresize class for anchor unti it added VFP. VFP's anchor works better than mine one. I don't build highly graphical forms. I'm an account developer and I don't have so much time for nice screens...