translation of / to / when extracting from sql server2005 db

[Peter]

I have an SSIS package which uses an OLE DB connection to a SQL Server 2005
database. It then runs a script component to manipulate the data before
writing the data to a flat file. One particular column has a / character in
the data and this is being translated to / (which is some sort of encoding I
think). The question is why is this happening.

The column is defined in the OLE DB input as being DT_STR with a codepage of
1252. The output column from the OLE DB setp has the same definition.

The script component has the same definition for its input and then has a
further input field definition which is used in the script component for the
amended data. The script component takes the input field length and appends
it to the input filed column using x.len & x.tostring (where x is the column).

The output file is created using a file connection and again has the input
and output fields defined as DT_STR with a codepage of 1252.

So, what is causing the encoding?

[Peter]

Even when I posted the encoded value this forum has translated it to a / -
it should say translated to ampersand,hash,four,7,semi-colon (without the
commas)!

Post by Peter
I have an SSIS package which uses an OLE DB connection to a SQL Server 2005
database. It then runs a script component to manipulate the data before
writing the data to a flat file. One particular column has a / character in
the data and this is being translated to / (which is some sort of encoding I
think). The question is why is this happening.
The column is defined in the OLE DB input as being DT_STR with a codepage of
1252. The output column from the OLE DB setp has the same definition.
The script component has the same definition for its input and then has a
further input field definition which is used in the script component for the
amended data. The script component takes the input field length and appends
it to the input filed column using x.len & x.tostring (where x is the column).
The output file is created using a file connection and again has the input
and output fields defined as DT_STR with a codepage of 1252.
So, what is causing the encoding?