>>Setting individual cells in flexgrid is a pain. Instead try binding to an ADO recordset or set text values directly in textmatrix array. Merging rows-cols as appropriate should also help.
>
>I'm not too familiar with ADO unfortunately, and learning might help simplify things a lot. I just keep putting it off, probably cause I'm lazy. =). In the full product I do use TextMatrix() for the setting of the text, but cell formatting requires the cell to be selected (to my knowledge)
>
>Even if I do manage to learn ADo I still need to be able to format the cells based on the data inside of them (Underlined for approved, italic for posted, etc.) Formatting such as this is a 'feature' of the product and so cannot be removed, and it appears that this feature is causing the problems. You can change the italic line in the code to bold or whatnot and the problems still arise.
>
>For the record merging has been done wherever possible. I've cut out the fat in as many places as I could think of, but the situation can still come up if the dataset is large and varied enough.
>
>If it's any help I'd also be willing to pitch a different grid to the boss if it would help matters any. As long as the grid has all of the same visual-formatting options I can probably work everything into it.
>
>And it figures I'd miss the "L" in the title. =\
>
>
>- Kevin Yockey

Kevin,
Right, cell formatting needs cell to be selected :( I meant if you can do it do per range of cells not individually.
Actually though if you don't need the 'merge' visual result do not use flexgrid at all IMHO (and possibly multiline headers). Native VFP grid is much better for the rest. ADO would only save you from data part.
One last thing, prefer Hflexgrid instead of flexgrid even if you don't need the hierarchical capability. Sounds Hflexgrid is more reliable.
Cetin