Add a task to save the number of columns in the 'current' file before its data flow is executed.

Add a suitable precedence constraint to avoid running the data flow task...

Run the 'guts' of your stored proc, having modified the final SELECT such that it does a

SELECT INTO [Newtable] .....

FROM etc etc

WHERE 1 = 0  --Don't...

Do the column names change from day to day?

If they do, do you want to create a new table every day?

Or is the target table static in structure such that...

Thanks Thom, quite right! I should have added the text "in this case".

Try adding

DROP TABLE IF EXISTS Response22;

before your CREATE TABLE statement.

Or change your CREATE TABLE statement to

TRUNCATE TABLE Response22;

Being picky, I do have a few other minor comments about the code:

1. The created table has no schema name
2. Literal dates are not in ISO format ('YYYYMMDD')
3. Inconsistent use...

Please check that both of the variables are being set correctly.

Try setting a breakpoint after the ExecSQL task so that you can inpect the runtime contents of your vSQLString variable ... perhaps that will throw some light on what is...

What is the data type of @[User::vDateThreshold]?

When you say: "I can see that it isn’t evaluating my variable correctly", what are you seeing, exactly\?

Yes, to examine what SSIS packages do, you need to open them in VS/SSDT.

I thought that IMEX=1 was valid for reading files, not writing to them. 

What problems do you see if you omit it?

CSV files are text files. They do not have sheets.

Three separate data flows, in series, to the same file, should do it.

There are no technical reasons why this would cause problems.

But if your spreadsheet users change the schema of the spreadsheet, as users tend to do, those changes will...