The behaviour seems to be the same in 2.0.
I did trace it, following the procedure in your nice MSDN article. The
DataSet trace records seemed routine, without any info about the computation
of the expression columns.

Thanks anyway,

Chris

> -----Original Message-----
> From: Unmoderated discussion of advanced .NET topics. [mailto:ADVANCED-
> [EMAIL PROTECTED] On Behalf Of Beauchemin, Bob
> Sent: June 1, 2005 10:43 AM
> To: [email protected]
> Subject: Re: [ADVANCED-DOTNET] ADO.NET Expression Columns - Aggregates of
> Aggregates
>
> If you are trying it on ADO.NET 2.0, why not trace it with the new tracing
> facility? It traces DataSet activity too.
>
> Bob
>
> -----Original Message-----
> From: Unmoderated discussion of advanced .NET topics. [mailto:ADVANCED-
> [EMAIL PROTECTED] On Behalf Of Chris Howlett
> Sent: Wednesday, June 01, 2005 4:19 AM
> To: [email protected]
> Subject: Re: [ADVANCED-DOTNET] ADO.NET Expression Columns - Aggregates of
> Aggregates
>
> That looks like an effective workaround. I'll try it.
>
> Thanks a lot Sebastien.
>
> Chris
>
> > -----Original Message-----
> > From: Unmoderated discussion of advanced .NET topics. [mailto:ADVANCED-
> > [EMAIL PROTECTED] On Behalf Of Sebastien Lorion
> > Sent: June 1, 2005 1:56 AM
> > To: [email protected]
> > Subject: Re: [ADVANCED-DOTNET] ADO.NET Expression Columns - Aggregates
> of
> > Aggregates
> >
> > We got the same behavior while working on a project using ADO.NET 1.1. I
> > don't know if it is fixed in .NET 2.0 or if it will stay the same "by
> > design". We got around using the hack below. We tried several
> alternatives
> > and it seems that only this one is bulletproof.
> >

===================================
This list is hosted by DevelopMentor�  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

Reply via email to