Re: DataTable.Select method bug (?) with .net framework 1.1 SP1

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: William \(Bill\) Vaughn (billvaRemoveThis_at_nwlink.com)
Date: 01/06/05 

Date: Thu, 6 Jan 2005 09:21:15 -0800

This is the best way to get their attention.
David? 

-- 
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"lynch" <lynch@discussions.microsoft.com> wrote in message 
news:E169E70D-684F-4EAD-BB37-FC188A6078A8@microsoft.com...
> Hi Bill.
>
> Some time ago I made some posts ofering a test harness so that the guys at
> Microsoft could find it easier to see the bug. My post was:
>
> "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 think it was a waste of time since aparentely Microsoft's efforts are
> elsewhere and noone even looked at the TH.
>
> I still find this hard to believe since we are MSDN Universal subscribers
> and I thought we were entitled an answer.
>
> I found a simple solution to the problem until the problem isn't solved by
> Microsoft and I think if everyone did the same maybe they would be forced 
> to
> take some action. Here is the snippet for those of you who can no longer
> wait. Just put the code at the entering point of your applications.
>
> if (IsFramework1Dot1SP1())
> {
>   throw new
> Exception(Library.Database.FRAMEWORK_1DOT1_SP1_UNSUPPORTED_ERROR);
> }
>
> public bool IsFramework1Dot1SP1()
> {
>   string runtimeVersion = System.Environment.Version.ToString(4);
>
>   if (runtimeVersion == "1.1.4322.2032")
>      return true;
>   else
>      return false;
> }
>
> "William (Bill) Vaughn" wrote:
>
>> Again, this bug was not mentioned at all at the conference. Apparently, 
>> no
>> one is seeing it.
>>
>> -- 
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant
>> Microsoft MVP
>> www.betav.com
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no 
>> rights.
>> __________________________________
>>
>> "Mayo" <Mayo@discussions.microsoft.com> wrote in message
>> news:DDDCE933-0E9C-4A8D-AFA2-4E9484FFEB81@microsoft.com...
>> > Hi, have you heard something from the Dev Connection Conference?
>> >
>> > "William (Bill) Vaughn" wrote:
>> >
>> >> I have heard  n o t h i n g. I'll see some of the folks at the Dev
>> >> Connections conference next week. I'll poll them there.
>> >>
>> >> -- 
>> >> ____________________________________
>> >> William (Bill) Vaughn
>> >> Author, Mentor, Consultant
>> >> Microsoft MVP
>> >> www.betav.com
>> >> Please reply only to the newsgroup so that others can benefit.
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >> __________________________________
>> >>
>> >> "Mayo" <Mayo@discussions.microsoft.com> wrote in message
>> >> news:0003A8CE-4419-4F17-98BC-62522F0061D5@microsoft.com...
>> >> > Is there any news on this thread up to now?
>> >> >
>> >> > "William (Bill) Vaughn" wrote:
>> >> >
>> >> >> I also told Microsoft about this and I'm monitoring this thread and
>> >> >> the
>> >> >> progress of the fix. I too think it's troubling.
>> >> >>
>> >> >> -- 
>> >> >> ____________________________________
>> >> >> William (Bill) Vaughn
>> >> >> Author, Mentor, Consultant
>> >> >> Microsoft MVP
>> >> >> www.betav.com
>> >> >> Please reply only to the newsgroup so that others can benefit.
>> >> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> >> rights.
>> >> >> __________________________________
>> >> >>
>> >> >> "Terry McGinty" <terrymcginty2000@yahoo.com> wrote in message
>> >> >> news:73a840e4.0410020952.6d8f172c@posting.google.com...
>> >> >> >> Just let me add something: if this is really a bug shouldn't 
>> >> >> >> some
>> >> >> >> action
>> >> >> >> be
>> >> >> >> taken from Microsoft urgently? People all over the world are
>> >> >> >> installing
>> >> >> >> SP1
>> >> >> >> as we speak. Many applications could break becouse of this (ours
>> >> >> >> did!).
>> >> >> >> This
>> >> >> >> could be worst than a virus in terms of $. Am I over reacting?
>> >> >> >>
>> >> >> >> Thanks
>> >> >> >
>> >> >> > No I don't think you're overreacting at all.  This bug brings to
>> >> >> > light
>> >> >> > a very serious issue.  I don't believe there is any way to 
>> >> >> > protect
>> >> >> > your application against a bug that shows up when a service pack 
>> >> >> > is
>> >> >> > applied to an existing version of the .Net Framework.
>> >> >> >
>> >> >> > The result is that you could distribute a solid, robust 
>> >> >> > application
>> >> >> > to
>> >> >> > thousands of users, but then wake up one morning to find that it 
>> >> >> > was
>> >> >> > starting to break everywhere through no fault of your own.  It's
>> >> >> > really a developers nightmare.
>> >> >> >
>> >> >> > Microsoft now knows about the problem with DataTable.Select(). 
>> >> >> > It
>> >> >> > will be interesting to learn how they suggest we deal with this 
>> >> >> > this
>> >> >> > type of service pack bug.
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

Relevant Pages