MSFlexGrid sorting bug.

[DP]

Hello,
Has anyone ever encountered the following sorting bug using the
MSFlexgrid ver. 6.0(SP3):

Before sort:
27.750
26.375
27.750
26.250
26.000
26.500
27.750
27.750
26.000

After sort:
27.750
26.375
27.750
26.500
27.750
27.750
26.250
26.000
26.000

Sort done with:
.Col = 38
.Row = 36
.Colsel = 38
.Rowsel = 44
.Cols = 39
.Rows = 188
.Sort = flexSortNumericDescending

Repeating the sort immediately after the first, produces a different
set of incorrect results.

Any ideas?

Thanks, DP.

[Chris Petchey]

Nope, I dont see that at all
I get:

27.750
27.750
27.750
27.750
26.500

26.375
26.250
26.000
26.000

You sure you using right cols and rows?

In article <b25c65a1.01120...@posting.google.com>, DP
<dxpa...@wthg.com> writes

--
Chris Petchey

[DP]

The data I gave is only a subset of the data in the grid. The given
data was the selected data I performed the sort on.

All the data in that column is in the format <##.###>, where # is a
numerical digit ranging from 0 to 9 (leading zeros are not shown, but
trailing zeros are), and zero is represented by <.000>.

Placing only the given values into a flexgrid and performing a sort
works fine. The sort fails when the column is densely populated with
values in the mentioned format. NOTE: only the
flexSortNumericDescending fails, not the flexSortNumericAscending.

Also, the sort produces inconsistent results. If I were to make a
selection and perform a sort, I would get a set of results, r1.
Leaving the same selection (r1 is selected) and performing the exact
same sort, I would get different results. Repeating the sort on the
same selection produces different results.

Hope that sheds some light.

Thank you for responding.

Chris Petchey <ch...@soltec.demon.co.uk> wrote in message news:<jt2iILEV...@soltec.demon.co.uk>...