DataTable.Select Bug in .Net Framework 1.1 SP1

[Guest]

Once again I'm submitting a bug introduced with .Net Framework 1.1 SP1 that
is breaking our application.
We use DataTable.Select method all over our application. One of the places
we use it is to filter some Entity information for permanent deletion from
the database!
We noticed that the code that worked perfectly for months stoped working
with SP1 of .Net Framework 1.1 with information loss since there were
database deletions!

We use loads of filters like this one:

"(HistoryStartDate >= #07/01/2004 00:00:00#) AND EntityId=7016 AND
FieldId=70 AND Deleted=0"

this worked perfectly without .Net Framework SP1 but not with SP1.

We have put together a Test Harness (with source code) at:

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

The sample default filter is the one specified above wich should return 0
rows when applied to the default sample data (TestData.XML - included with
the Test Harness). The problem is that the Date part of the filter doesn't
work properly and rows are returned.

If you try to apply just the Date part of the filter to the same sample data
no rows are returned (the expected result!).

I have seen other threads reporting this problem but it seems like the guys
at Microsoft aren't very concerned since there are no replies.

If someone out there could help I would very mutch appreciate it. I tried
everything I could remember but made no progress. This is a very serious
problem for us.

Thanks in advance.

 

[Guest]

I have seen other threads reporting this problem but it seems like the guys

at Microsoft aren't very concerned since there are no replies.

It is not wise to assume based on limited exposure. ;->

I do not have SP1 on this machine. If I could hook up the laptop here, I
would go ahead and see if I could catalog this issue, but I will have to wait
until tonight to get it hooked up.

---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

 

[Guest]

If you want you could post your problem to product support.

http://support.microsoft.com/

Be sure to have your licence key, ect... ready.
I did it once for a bug and the system works fine, but it can take a little
effort from you side to (make a testcase 100% repro)...

Shorty

 

[Guest]

I know and I'm sorry!

I think I'm kind of upset: each day our clients are upgrading their
Microsoft .Net Framework 1.1 to SP1 and then calling us in panic because of
data loss or corrupted data... It's becoming quite a big problem for us!

Thank you

 

[Terry McGinty]

I agree this is a very serious bug. As I responded in another post
concerning this issue, I too am having this problem with a similar
expression:

ReviewID = 5 AND ReviewType = 'RSF' AND AnchoredTo = 1 AND
ReviewNumber > 4

The filter is not evaluating the last expression (ReviewNumber > 4).
Before I installed SP1 and SP3, this expression worked fine.

My conclusion was that the Select() filter can now only handle 2 AND
clauses.

Terry