There is a bug in .Net Framework 1.1 SP1 with the DataTable.Select method.

Microsoft's description of the problem may be found here

http://support.microsoft.com/default...b;en-us;891742

and you can ask for a fix to that issue. The problem is that the fix does
not work properly!

Some problems were solved with this fix but some persist. And the problem
relates to the overload of DataTable.Select with a filter and a sort
expression: in that case the result of the method returns rows that do not
meet the filter conditions.

We have a detailed description of this problem at :

http://pwp.netcabo.pt/0434926301/

and have included a new test harness (source code included) to test the
problems we are experiencing.

As we can't tell for sure what gets solved and what doesn't with this fix we
decided to continue limiting the support for our applications for clients not
running the SP1 of the .Net Framework 1.1.

The purpose of this thread is to notify microsoft for the problem so that an
effective fix is released and to alert the developer community for this very
harmful bug.

The first thread I know of reporting this problem dates from 9/9/2004 and
Microsoft still hasn't fixed the problem...

Thanks Lynch for reporting, we will investigate this issue.

--
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.


"lynch" <(E-Mail Removed)> wrote in message
news:B5DDDFBC-169B-4FEB-BFC8-(E-Mail Removed)...
> There is a bug in .Net Framework 1.1 SP1 with the DataTable.Select method.
>
> Microsoft's description of the problem may be found here
>
> http://support.microsoft.com/default...b;en-us;891742
>
> and you can ask for a fix to that issue. The problem is that the fix does
> not work properly!
>
> Some problems were solved with this fix but some persist. And the problem
> relates to the overload of DataTable.Select with a filter and a sort
> expression: in that case the result of the method returns rows that do not
> meet the filter conditions.
>
> We have a detailed description of this problem at :
>
> http://pwp.netcabo.pt/0434926301/
>
> and have included a new test harness (source code included) to test the
> problems we are experiencing.
>
> As we can't tell for sure what gets solved and what doesn't with this fix
> we
> decided to continue limiting the support for our applications for clients
> not
> running the SP1 of the .Net Framework 1.1.
>
> The purpose of this thread is to notify microsoft for the problem so that
> an
> effective fix is released and to alert the developer community for this
> very
> harmful bug.
>
> The first thread I know of reporting this problem dates from 9/9/2004 and
> Microsoft still hasn't fixed the problem...
>