|
Posted by Runner on 10/02/36 11:45
JayCallas@hotmail.com wrote:
> So then I am screwed... Bummer.
I am not sure if your options would include this but please do check
out CampaignRunner. It does what you are trying to accomplish easily
and across a number of different systems.
Sincerely,
> 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..)
Navigation:
[Reply to this message]
|