>>>Narrow down all that to a simple SELECT and then return either an ADO.Net record set or an EF entity.
>>>
>>
>>I found some samples using DataTable and also apparently we have methods that operate with the datatable, so I am going to proceed this route.
>
>You could probably write this in t sql while you were reading the paper in the morning. Why mess with C# / ADO. Just munge the data on the back end an return the product (or, for that matter, return XML)

The return results depends on the passed type so I plan to return a result set anyway (although I can munch it in T-SQL also). But you're right, I'll go now with the T-SQL solution. Still playing with ADO.NET gives me some experience and I can at least see I can get the result this way also. But probably should not have wasted the time.