>>>Hi Folks,
>>>
>>>I'm lost. I have an app (GoFish) that sets a grid to a controlsource. This is as simple as
>>>

>>>loGrid.ColumnCount = Fcount(Thisform.cSearchResultsAlias)
>>>loGrid.RecordSource = (Thisform.cSearchResultsAlias)
>>>

>>>The grid itself has a number of columns at design time, oddly set columnorder, oddly set zorder. Some have a column order some not. The number is different to the one set above.
>>>
>>>The column Column17 appears left most and will be the first instantiated. It gets the 3th column of the table. Even when I change the table. It's all time the third.
>>>Why? Why the third?
>>>
>>
>>Because ColumnOrder is set to 3 for that column.
>>
>>Tamar
>
>ColumnOrder is determining the column of the cursor to pick? It's about visibly sorting the columns! There is not a single word in the help on this. And, since I never do this, because design time handling grids with dynamics odd at least I had never a chance to see this.
>I'm to old for this kind of feature.
>
>So how in relation of columnorder and zorder does this work? The grid has columns with and without ColumnOrder set, and ZOrder is special as well? How does it end up?

Is it possible that there's a custom column class involved? I've seen cases when it was used, funny things would happen when instantiating those, in unfathomable order, even the class level .init() being executed instead of instance's (which may not fire at all). I know I ended up with grids with lots of code in grid.init() and no columns set in the designer. At least I had control over the course of instantiation.