August 11, 2014 at 4:27 am
It is strange when its not working for one particular date alone.
The derived column expression looks fine to me.
What is your source connection and what format you are reading the column there? How did you identify it is parsing it wrong.
August 11, 2014 at 4:46 am
ronan.healy (8/11/2014)
a right ya sorry was getting mixed up.but the date has to be in the mmddyyyy for the system it goes into when the package runs
You mentioned earlier that the destination was 'sql' - from which I assumed SQL Server. Based on this comment, I am assuming some other DB engine - is that correct?
Either that, or the datatype of the destination column is not date/datetime/datetime2?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply