|
Posted by Erland Sommarskog on 10/02/37 11:45
(JayCallas@hotmail.com) writes:
> So then I am screwed... Bummer.
>
> The stored procedure is simple enough but it uses that function to JOIN
> against the comma-separated turned temp table... which throws the
> error.
>
> (The reason we use FMTONLY to get the schema is because we do not want
> to roll out a new version of the app each time we add/remove a column
> from the resultset. An add-in to Excel that we wrote allows the users
> to drop data into a spreadsheet. Using the schema, we give the user the
> ability to select which columns they want to see and in which order.)
>
> A workaround seems to be to make sure that the "sample" list passed to
> the stored proc contains at least two values... (need to have that
> comma in there to keep the error from happening..)
Or try to change the function so it does not blow up with FMTONLY
on...
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|