>The Excel file should "automatically be saved" when the Excel Destination component succeeds
I agree.
>Is the File System Task source coming from a variable or from a connection manager?
I couldn't do the fso task with the connection, as for some reason when Source Connection / IsSourcePathVariable=False
My way around this was to have a script task up front that dumps the path into various variables, so my fso tasks can use the path in the variable values.
>I'm thinking somehow the files aren't exactly what they're supposed to be so it's maybe creating a blank Excel file
Not happening. My .xls has two tabs, Info and Data. Info is some developer love notes, and data is the recordset.
On all copied files, the Info tab is an exact copy, the Data tab column headers in row 1 are there, just not the data in row 2 downwards.
Main Topics
Browse All Topics





by: stelth240Posted on 2009-06-19 at 18:48:59ID: 24671427
The Excel file should "automatically be saved" when the Excel Destination component succeeds. I put quotes around that because it doesn't actually save it, it's exported to Excel continually until the pipeline is finished.
I was thinking maybe the source of the File System Task isn't pointing to the correct source Excel file, but I was thinking you probably made sure it is. Is the File System Task source coming from a variable or from a connection manager? I'm thinking somehow the files aren't exactly what they're supposed to be so it's maybe creating a blank Excel file as opposed to the one that would contain the data.
I did a test with Excel to make sure it does work, and the File System Task did copy the xls file with all the data.
Let me know what your setup is (the FIle System Task properties and the variables/connections involved).