The version of VB.NET used in SSIS is, I believe, called VB.NET for Applications and is not the full-blown development environment in which you have developed your earlier piece of...

If this is pure numeric data in a CSV file, it should not be surrounded by text qualifiers ("). Try stripping these text qualifiers out from this field.

Phil

I had a quick look at the code: so for selected rows in a source SQL Server table you are executing an FTP process?

You need to get yourself on an...

As you have things up and working, you've probably lost the urge to change how it operates now (I know I would!).

And given that you have so few source records,...

The script task, as you have discovered, is just a place where you write VB.NET code and was, I believe, included to cover those situations where the other SSIS components...

Just use a lookup from your source 'Item' data to retrieve the ID of the newly created Item and then use that to populate your ItemComments. No need for the...

If it's numeric, cast to integer, otherwise leave as is:

declare @value varchar(10)

Set @Value = '0000006708'

if IsNumeric(@value) = 1

select cast(@value as integer)

else

select @value

Phil

Not hard with a script component. Here's a snippet - assumes variables declared and strFilepath, strFilename have been set:

'Connect to the CSV file and...

What do you want to do in those cases where the date is invalid? Error? Import the record with a null date?

You want to execute a query that returns a resultset and iterate around that? Can you provide more detail about what you are trying to achieve?

Excellent! Good to hear.

Phil

Now I see what you're asking.

Well - you could create pack3.dtsx and in it create two linked 'Execute Package' tasks which execute Pack1 and then Pack2.

Or ... you could go...

I think people misunderstood your first post a little - you suggested that there could be varying numbers of fields on each record. To accommodate that scenario, scripting would be...

SSIS will eat that up, no problem - that is standard CSV format. The fact that many of the source fields are NULL just needs to be accommodated as part...

Michael gave you the answer. Change your destination component to be SQL Server, not OLEDB, and the option is there.

Phil