I've been using the new SQL-LINQ feature in ASP.NET and recently came across the following error message when calling a stored procedure from the SQL to LINQ data class: "The required column <ColumnName> does not exist in the results" The strange thing was this seemed to work fine when I called the stored procedure directly in SQL, but threw an exception when called in C#. After a night's sleep, I figured out what the problem was: The stored procedure was pretty meaty but basically the following ......