Well, the internal implicit conversion changed the column99's datatype to NText automatically in the source editor, so I had to change the destination datatype to NText to match them. ...

My destination is a table in SQL server. My query is against the source, which is our ERP server. This package pulls data from ERP source into SQL server.

The column...

Sorry, that's my destination.

Steve, Not sure how to provide table schema.

My table structure is

[dbo].[table1](

[column1] [nvarchar](3) NULL,

[column2] [nvarchar](4) NULL,

[column3] [nvarchar](10) NULL,

[column4] [datetime] NULL,

[column5] [nvarchar](10) NULL,

[column6] [nvarchar](4) NULL,

[column7] [nvarchar](10) NULL,

[column8] [int] NULL,

[column9] [datetime]...

Source is data connection from a PC from which ETL is performed.

I tried various other things, like deleting the mapping between external and output columns in the ADO NET...

Sorry for the delay....but I followed what you'd said and it returned this:

[ADO NET Source [2]] Error: The ADO NET Source was unable to process the data. Field table-column99 is...

Description: The ADO NET Source was unable to process the data. Field table1-column99 is missing an escape character for a quote.Unable to update PK WHERE clause.Error processing data batch. ...

I tried doing that too, excluding the column99 in the select list in the ADO NET source. But it still throws the same error.