>Can you post at least one reference with the wrong answer?

Here one of many
http://stackoverflow.com/questions/209383/select-columns-from-result-set-of-stored-procedure


>
>There can be wrong answers somewhere, but I doubt you should get them on a first page in either of the search engines. Unless you started with the very wrong search term.
>
>BTW, for sharing data between stored procedures I suggest to read this classical article
>How to share data between stored procedures

Thanks. It was this page that got me in the right direction.

>
>>After searching some more, I found that syntax. It worked, and now I am back coding and not searching.
>>
>>I wonder why the other syntax is plastered all over the internet in referance to SQL 2008 if it is not valid? Sometimes I get frustrated when I encounter answers on the web that either unrelatered or flat out wrong.
>>
>>Thank for the reply.
>>
>>>It's invalid syntax. You have to create a [temp] table with columns that match SP recordset first and then
>>>

>>>INSERT INTO <table name> EXEC [mySP] 'para1'
>>>

>>>
>>>
>>>>I have several individual stored procedures that are related. I am looking to select from them all into a single select statement result. The syntax I have noticed all over the web suggests
>>>>
>>>>

>>>>SELECT * FROM EXEC [mySP] 'para1'
>>>>

>>>>
>>>>But, SQL Server tells me that it is a syntax error to use the EXEC in the data source in the above statement. Is there some setting I must configure before this type of syntax is accepted?