>>Lots of times I've said 'I don't use such-and-such' because it can't do so-and-so' only to be told that it can. And if I'd never made the statement in the first place I might neve have found out. :-}
>
>Yep. Good point!
>
>>The designer basically creates a method (with default name the same as the SPROC name) on the DataContext with the method taking that same parameters that are required by the SPROC. So you don't use a select to retreive. More like:

>>List<things> = DataContext.ProcedureName(param1, param2);

This link describes better and in more detail:http://weblogs.asp.net/scottgu/archive/2007/08/16/linq-to-sql-part-6-retrieving-data-using-stored-procedures.aspx
>
>Good article (Scott is always a good read). I should probably take the time to explore this a little more. I don't think we'll be changing our Framework any time soon (lots of reasons for that decision, I won't bore you with details), but it might be good to get a better feel for how this might work for us in the future.
>
>Thanks for the info Viv! =0)

TBH, I knew you could do it but had forgotten the exact way it worked so had to look it up (I've moved to trying out the Entity Framework which seems to be the way the wind is blowing)
Best,
Viv