M
Marina
Hi,
I have an expression column (integer). This column gets populated
correctly.
I then have a Select, that is:
dt.Select("Calc = " & dt.Compute("Min(Calc)", "") & "")
Now, as you see, first I am computing the minimum value of the column, and
then using that in the select. Now, this HAS to return at least 1 row,
since Compute is returning the value in one of the rows, hence Select has to
find that row.
But, for certain number it does not. Now, I can clearly see in the
debugger, that dt.Rows(121)("Calc") = 1514. I can also see that
Compute("Min(Calc)", "") = 1514. So they are completely identical. So, at
the very least, Select should return the 121'st row.
In my debugger, I try to Select other known values of Calc. Some of them
are found correctly - but others, just like 1514, are not.
As I've never experienced a problem with Select and regular fields, my
thinking is that this is some sort of odd expression field bug?
Any ideas?
I have an expression column (integer). This column gets populated
correctly.
I then have a Select, that is:
dt.Select("Calc = " & dt.Compute("Min(Calc)", "") & "")
Now, as you see, first I am computing the minimum value of the column, and
then using that in the select. Now, this HAS to return at least 1 row,
since Compute is returning the value in one of the rows, hence Select has to
find that row.
But, for certain number it does not. Now, I can clearly see in the
debugger, that dt.Rows(121)("Calc") = 1514. I can also see that
Compute("Min(Calc)", "") = 1514. So they are completely identical. So, at
the very least, Select should return the 121'st row.
In my debugger, I try to Select other known values of Calc. Some of them
are found correctly - but others, just like 1514, are not.
As I've never experienced a problem with Select and regular fields, my
thinking is that this is some sort of odd expression field bug?
Any ideas?