D
Dallara
FYI
This is about a bug in DataTable.Select, where the wrong rows were returned
from this function, which I reported here a time ago and was completely
ignored (some guys from US even complained about me referring to "(" and ")"
as brackets as opposed to parenthesis).
Anyway, I've reported the bug to the Whidbey bugs page, and they fixed it.
http://support.microsoft.com/default.aspx?scid=kb;en-us;891742
FIX: Multiple conditions that use the AND operator and that are passed to
the Select method of the DataTable object may be ignored after you install
the .NET Framework 1.1 Service Pack 1.
SYMPTOMS
After you install Service Pack 1 for the Microsoft .NET Framework 1.1,
multiple conditions may use the AND operator. When these conditions are
passed to the Select method of the DataTable object, they may be ignored.
The Select method returns a result that contains incorrect records instead
of the records that you would expect if all conditions were considered.
Thanks,
Dalmo
This is about a bug in DataTable.Select, where the wrong rows were returned
from this function, which I reported here a time ago and was completely
ignored (some guys from US even complained about me referring to "(" and ")"
as brackets as opposed to parenthesis).
Anyway, I've reported the bug to the Whidbey bugs page, and they fixed it.
http://support.microsoft.com/default.aspx?scid=kb;en-us;891742
FIX: Multiple conditions that use the AND operator and that are passed to
the Select method of the DataTable object may be ignored after you install
the .NET Framework 1.1 Service Pack 1.
SYMPTOMS
After you install Service Pack 1 for the Microsoft .NET Framework 1.1,
multiple conditions may use the AND operator. When these conditions are
passed to the Select method of the DataTable object, they may be ignored.
The Select method returns a result that contains incorrect records instead
of the records that you would expect if all conditions were considered.
Thanks,
Dalmo