>But I have two questions.
>
>1. Can this be used with the visual designer, which I don't want to lose? The examples use code to create the columns; can I use this with a Grid in the visual designer, i.e., MODIFY FORM?
>
>2. From the manual: "... When these properties are set, new member objects inherit from the specified member class. ..." Does "new member objects" mean I have to delete columns and add them again, so they use the specified memberclass?

Q1 - I don't think you can use the visual designer for the column class; I believe it has to be a program based class. For the page, optionbutton and commandbutton you can use the visual designer for classes.

Q2 - What happens is that any columns, headers, and textboxes (or any other object such as checkboxes) are removed from the grid object, then new objects for the columns, headers, and textboxes are added based on the memberclasslibrary. Any code that was in the previous objects is deleted with the deleted objects. So if you want to change the memberclass and you have code that you want to keep, you have to move it into the memberclasslibrary or copy it to a external file and then readd after the new memberclass based objects are added.

One of the nice benefits of the memberclass property is that any new columns that are added automatically inherit the code in the memberclass library. The downside is that when you have an existing grid (such as your case) that has code already in it, then you have to move the code out and put back in order to use the memberclass advantages.