Posted by JayCallas on 10/02/34 11:45

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..)

[Back to original message]