>>>>woops i misspoke...
>>>>I have a grid which i set the HeaderHeight property to 40 and the Header Wordwrap property to true. It looks perfect at design time time but goes fubar at runtime. My first thought was that the grid was being destroyed somehow and reconstructing, but i keep disabusing my self of that notion. I don't seem to be able to work it out. Some light in the darkness would be greatly appreciated.
>>>
>>>And what would happen if you set the hederheight in the init of the grid ?
>>
>>walter thanks for replying. I get the same result.
>
>If .columnClass and .columnClasLib (or whatever the exact names may be) are set, the instance code may fire _after_ everything is instantiated, and the column class's .init() may fire even though it may be overridden in the instance or in the grid's code. These two heavily disturb the regular order of code when instantiating the columns (and probably same for pages), so yup, more tricks in the grids.

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

Type("ogrid")+Type("ogrid.Column1.HeaderClass")  ;
+iif(Type("ogrid.HeaderHight")=="N", str(ogrid.HeaderHight), "U")

? This way indication should be given whenever something changes. As grids are already hard to follow, .HeaderHight_Assign() might help but also throw more wrenches into the fray...