Marcia,

I tried a search of MSDN (library, July 2001) using "column0" and came up with 1 entry for "Office".

Based on your last sentence I would have expected to find a listing in MSDN for the problem.

Do you have any idea why it isn't there?

Jim Nelson


>Hi Mike.
>
>>> I created a pageframe class and placed several grids on the different pages so I can see where the record pointers are in each of the tables. I've also hard coded the ColumnCount and RecordSource in each of the grids and set the ControlSource for each column.
>
>Now the interesting part. VFP insists on inserting a Column0 in EVERY grid when I drop it on the form. When I run the application Column0 contains the unique id field used in the DE relationship. Anyone know why this happens or how to prevent it? <<
>
>This is a known bug. Andy Kramek and Christof Lange worked this one out in Orlando in 1998. To the best of my recollection, the problem is caused by having the ColumnCount set to a non-zero value in the grid class.
>
>Adding this:
>
>

>IF TYPE( 'This.Column0' )= 'O' and NOT IsNull( This.Column0 )
> This.RemoveObject( 'Column0' )
>ENDIF
>

>
>to the init of your grid class should remove the extra column.
>
>BTW, did you also find that all the headers in your grid had been reset to theit default settings? That was the case with this bug (Yes, it IS a bug) back in 1998.