Hi Glenn,

Thanks for the reply. What do you mean by "drilling down the containership hierarchy"?

I can see how SYS(1272) works to tell you what the hierarchy is for an object. And I assumed that SYS functions were all old FoxBase stuff... Didn't even think that they had added more...

John

>To save various user settings you can untilize a "RESOURCE" table loosely structured as follows:
>
>USERID C
>FORMID C
>FORMTOP I
>FORMLEFT I
>FORMWIDTH I
>FORMHEIGHT I
>GRIDARRAY M
>
> In your base form class add code to the DESTROY event which captures the above settings. Define an array to hold grid settings. By drilling down the containership hierarchy locate each grid and create an array row. Each row could be structured as follows:
>
>grid reference ( thisform.container1.container2.grid1 ) hint ( sys(1272) )
>columnstring C1,O99,W999;C2,O99,W999...
>
>After saving the grid data to the array, store the array to the Memo field.
>
>Add code to the INIT event of your base form class to attempt to retrieve a record from the "RESOURCE" file and if found apply the saved info.
>
>
>>How can I store the ColumnOrder and Width when the user modifies a grid?
>>
>>Thanks