date parse error and tSchemaComplianceCheck

[Anonymous]

Hello!
As I've started the real work, more and more issues are coming up, sorry for bothering all the time
Well I have another issue when I enter a "error causing" - line into my test- input file: there is a Date in it which, for example is filled with "ffffff" instead of "24112008" for example.
I'm also using a tSchemaComplianceCheck - component which should help to write out a message into a special (delimited) file when the fields in a row don't have the correct format.
But now, the date parsing error is thrown earlier, in the tFileInputPositional - component and so there is a "parse error" - message written to system out/system error but as this wrong sentence never reaches the tSchemaComplianceCheck, the error is never written ino the delimited file.
Is there any other possibility to make this work?
Thank you in advance,
Stefan

[alevy]

Just change the date pattern of the output component.

[Anonymous]

Does the tschemacompliancecheck only work with strings?  I am having the same problem as CrazyBird in TOS V. 5.6.1
I have dates coming in via tfileinputdelimted and entering the tschemacompliancecheck which has the custom defined option selected.  The "type" for the date column is set to date and the "date pattern" is "yyyy-MM-dd".  However the bad dates are not getting rejected and I am getting NumberFormatException errors from the job.