>Hi Gregory
>
>>Grid.Destroy() is fine - been doing it for years. Doesn't destroy go from outer to inner ? - which means there are still columns when the grid destroys
>
>Grid.Destory() for me is 0 for column count for both the msgbox():
>

MESSAGEBOX(this.ColumnCount)
>
>DODEFAULT()
>
>MESSAGEBOX(this.ColumnCount)

For a while I tried to have each column save its own width and order, from column.destroy(), but that was too late - the grid didn't exist, and the .columnorder would be zero. So I've added a .cleanup() method to my column class, which just writes these two numbers to the .ini file. The .cleanup() for each column is called from grid.destroy().

One thing that may be different - my grids are built up, i.e. they have zero columns at some point (i.e. even when they start as normal grids, they have their columns replaced with my columns), and the columns are addobject()ed.