It seems this would have been easy to add. Personally I would have preferred a native
high-light row to the grid. Also, I would have liked them to break-out the BeforeRowColChange and
AfterRowColChange into BeforeRowChange/AfterRowChange, etc. Additionally, I would have
liked more array like control and handling of the grid data. On and on and on. If we added
all theses and more what would we have traded it out for (ADO, component gallery, assert,
assigns, etc)? Just like it is in prioritizing projects in a corporate environment prioritizing is an
impossible task. Sometimes an easy feature doesn't get included because it is part of
a whole group of enhancements.

I am not sure comparing one feature that PowerBuilder has and VFP doesn't is fair. I think
we would have to compare feature by feature and then contrast the have's and have not's.
Essentially that is why I am coding in VFP instead of PowerBuilder.
========================
>>I, for one, would not really want them to add features if they are close to shipping the product. Additional features can add bugs. I want stability at this point more than anything.
>
>Good point :) The multiline header has been on the wish list for years by a wide number of developers, though...PB got the capability over a year ago. It seems odd that the vfp team can't implement it by now...
>
>Most situations developers can build their own classes with workarounds, etc., but this particular feature is not simple...I've been trying to build one the last few days, or at least analyze what the requirements entail. The stretching is easy, but the moving of columns is not a trivial project...