Re: using SELECT to call a STORED PROCEDURE

The behavior you're seeing is correct. A stored procedure can only return a single value when called as a function via SELECT. Have you considered calling your procedure prior to the select, having it create a [temp] table and joining to that table with your original select? You could even create a view which joins the original table with the one populated from the stored procedure to make the join transparent to you or your users. Regards, bc