I don't have 6, so I'm afraid I can't answer any of those questions. I hope the ro/c works for you. Don't worry about the number of questions. That's what this place is here for.

-Michelle

>Based upon my investigations and your conclusions, the removeobject/column method is worth trying. However, I seem to remember there being a problem in one of the versions of FoxPro regarding the removing an object and adding another object of the same type with the same name. Does anyone know whether this was actually a problem and, if so, has it been resolved in version 6.0
>
>Whilst it is in my mind, here is another little thing which I don't quite understand regarding grids and VFP 6.0.
>
>1) Create a Form Class (using the Class Designer)
>2) On the Class place a grid (custom or base - it seems not to matter)
>3) Save the Class.
>4) Use the Form Designer to create a new form based upon this grid class.
>5) Use any table that you wish and bind a couple of columns to the grid on the Form.
>6) Not using the Data Environment of the Form, put code to open the table in the Load Event of the Form (Theoretically, this Event should be performed before the Forms objects are instantiated, allowing the controls which may be bound to the table to "see" it.)
>7) Run the form.
>
>Does it work???
>
>If it doesn't and you have a version of VFP 5.0 hanging around, run the same form unmodified in 5.0.
>
>Do this work??
>
>Answers on a email!!!
>
>P.S. I am sorry to bombard you with so many questions, but its nice to have someone to talk to!! (not that I'm a sad, lonely, individual, with no one who loves me...Sorry, I digress)
>
>Once again many thanks.
>
>Clinton