Dimitris,

What Dimitry posted is a good solution, but I'd say it's better to give a grid subclass the ability to save restore it's settings. Read them from the persistent store you use (system registry or table) in the grid.Init() and save them to the store in the grid.Destroy()

>I was trying to "persist" a grid object meaning to save the modifications of the grid made by the users by using the saveasclass method, but i have problems with it. Here is the scenario:
>1. you cannot save the class with the same name when it is beeing used
>2. The aboved has been solved by saveasclass() with different name removing the referenced class from memory deleting it from the library and renaming the saved class to the original.
>3. Still VFP seems to beeing saving the original class definitions (not the modified properties ...)
>What is happening here??? How to have a (sort of) object persistense in VFP?