On May 10, 11:21 am, Wade.Grau...@gmail.com wrote:
> I'm trying to map two source columns into one destination column but
> it won't work. Basically my source is a CSV file that has an Area
> Code field and a Phone field. I want to combine them into one field
> for the destination sql table of my DTS job but it won't take.
>
> 'The following doesn't work.
> Function Main()
> DTSDestination("Phone") = DTSSource("Area Code") & DTSSource("Phone")
> Main = DTSTransformStat_OK
> End Function
>
> But if I keep it one to one it works!
>
> 'This works.
> Function Main()
> DTSDestination("Phone") = DTSSource("Phone")
> Main = DTSTransformStat_OK
> End Function
>
> I think the DTSSource("Area Code") field is not visible to the above
> transformation between DTSDestination("Phone") and DTSSource("Phone")
>
> I know I could create a temporary but initial destination table, dump
> the CVS into this table and then run some SQL to combine the columns
> and then clear and dump this into my true destination table, but
> there's gotta be a better way.
>
> Does anyone have a simple solution for this?

> I'm trying to map two source columns into one destination column but
> it won't work. Basically my source is a CSV file that has an Area
> Code field and a Phone field. I want to combine them into one field
> for the destination sql table of my DTS job but it won't take.
>
> 'The following doesn't work.
> Function Main()
> DTSDestination("Phone") = DTSSource("Area Code") & DTSSource("Phone")
> Main = DTSTransformStat_OK
> End Function
> But if I keep it one to one it works!
>
> 'This works.
> Function Main()
> DTSDestination("Phone") = DTSSource("Phone")
> Main = DTSTransformStat_OK
> End Function
> I think the DTSSource("Area Code") field is not visible to the above
> transformation between DTSDestination("Phone") and DTSSource("Phone")
>
> I know I could create a temporary but initial destination table, dump
> the CVS into this table and then run some SQL to combine the columns
> and then clear and dump this into my true destination table, but
> there's gotta be a better way.
>
> Does anyone have a simple solution for this?
>