>>Don't do databases with LINQ. LINQ to SQL is essentially dead. The syntax will also be different in C# than VB. Which are you looking for?
>
>Somebody here told me to use Linq rather the traditonial scanning through the traditional ado.net recordset to aggregate information from a database extraction.
>
>Now I'm puzzled. And I'm working in vb.net btw.
>
>This seems to work for me btw (osql.execute extracts an access query in a datatable osql.dt).
>
>

> 
>        Dim osql As New sqlClass : osql.Execute("qryBestelKK")
>        Dim orders As IEnumerable(Of DataRow) = osql.dt.AsEnumerable
>
>        Dim test = From r In orders _
>                   Group r By name = r.Field(Of String)("KL_Naam") _
>                   Into g = Group Select New With {.Name = name, .total = g.Sum(Function(r) r.Field(Of Decimal)("Bestd_Waarde"))}
>
>        For Each r In test
>            Console.WriteLine("name: {0} total {1}", r.Name, r.total)
>        Next
>

>
>Can't begin to imagine why you would say Linq is dead. It is sooooo straightforward :)

Whoops! Go back and check. He said linq to SQL is dead.

>
>BTW this is just one of the manipulation I do on that table, but the others are scalars, and they were easier to figure out.
>
>Thanks for caring.
>
>>
>>
>>>Could somebody translate
>>>
>>>

>>>select Kl_Nummer,ArtBtw,sum(bestd_waarde) as netto from [somtable] group by kl_nummer,ArtBtw
>>>

>>>
>>>into linq?
>>>
>>>Thanks. Just need to see it done once, or refer me to a link (no pun intended)