>>>Naomi just prefers that you do the work for her, hehe...
>>>
>>>+++ Rick ---
>>>
>>
>>I know and I keep telling myself I'm not getting involved anymore, so this time its for real... LOL....
>
>Aside from points already made, have to bring this up - why traditional SQL (either pass through or stored proc) isn't being used.
I just don't see the business case for using something where there's constant fiddling with syntax. (Not asking you specifically, just a rhetorical question). I've never been a fan of SQL-like syntax in LINQ and these are the reasons why.

OTOH, why clutter up the server with potentially dozens of SP's the results of which may only be needed by one developer in one part of an application ?

Conversely, if an SP is used there's a much greater possibility that a developer (or a DBA) may modify it to suit some specific need without realizing that it could impact on another area of the app.

And I don't think the reference to 'constant fiddling' is relevant. Admittedly Naomi could probably whip up a SP in less time - conversely I'd be constantly fiddling with the T-SQL syntax :-{