>>Hmmm, would a guarded expression set to break on change be a better way to follow property value changes in the debugger ? Something easy like

>>iif(Type("ogrid.HeaderHight")=="N", "N"+str(ogrid.HeaderHight), "U")
>>

>>set up in debugger BEFORE grid instance is created to trace all changes or if more tricks with memberclasses either on column and/or header on grid construction are thrown into he blender, trace a bit more
>
>I'm pretty sure this would work but wouldn't show anything. The variable oGrid is not assigned a reference until the grid.init() exits, and then it may already be too late - whatever happened while building the grid is probably already finished. Even somewhere in grid.init() may be too late, if the thing happens somewhere in header's class's init, or column's. Though, the affected property being .headerHeight, well, perhaps grid.init() isn't a bad place at all.

Could be - or a global reference in grid.Column1.Header1.Init could be assigned. Still patchwork - better the patchwork after form is done from other post, should be simple

function headermultiline(toGrid)
toGrid.setall("WordWrap", .t.) && unless wrappable controls in grid 
toGrid.HeaderHeight = m.toGrid.HeaderHeight * 2

if only 2 lines for header caption are needed. Of course not dynamic, but that could probably also be added...