I'm using VFP 7.0
I designing my own resize class.

The resize classes that I've seen all resize the parent before drilling down and resizing the children.
Is there any reason I shouldn't drill down and resize the children before the parent?

Method AdjustSize(toObject)
  local lo
  if pemstatus(toObject,'Objects',5)
    for each lo in toObject.Objects
      this.AdjustSize(lo)
    endfor
  endif
  .... resize toObject

I'm asking because I have a client that wants to see the grid centered in the pageframe and doesn't want extra space in the grid after resizing. So the grid.Width has to be calculated after resizing all the columns (because Recordmark, DeleteMark, and ScrollBars don't resize), and the Pageframe needs to know the final width of the grid in order to resize properly, and the Form needs to know the final width of the Pageframe in order to resize properly.

I am having problems drilling down in a grid first and I'm guessing that it's because some properties are carried down from the grid to the column to the control (Fontsize specifically), so they need to be set at the grid level first.

TIA