Error Row Redirection...at Destination

I know how to setup the components to redirect error rows. Unfortunately, you can only redirect error rows coming through a transform. The only ones you can actually redirect going from a transform to a data destination are things like violations of a primary/foreign key. However, redirection does not work if you have a row come through a transform to a destination and the error is a constraint violation like trying to stick a null into a not null column. This simply makes the entire thing fail and shut down instead of redirecting just the row which failed.

This is the specific case. I have a really messed up inbound file. The file is pipe delimited and at least every row is the same length. I bring the file in and shove the entire file through a derived column task to explicitly calculate nulls since I can't get the convert data task to handle it and I didn't want to rewire the entire package. From there the data flows into my first conditional split where I look at the 4th column of data and split off the rows for a specific record type. These rows flow through a convert data task to do the data type conversion specific to that record type and then flow into an OLE DB destination adapter. The remaining rows flow down into a derived column transform to do some additional scrubbing for the remaining record types. From there, it flows into a conditional split to split the records out 16 ways based on the value in the 4th column, with anything not matching being dumped back to an error file for someone to look at. Each leg of the conditional split sends the row through a convert data task to convert the data to the data types specific to that given record type. I have error files setup for each of these off the convert data task which redirect any row that fails conversion. This redirects any row which doesn't convert properly. It also succeeds in redirecting any row which violates a primary or foreign key constraint. However, it does not handle those cases where the inbound file had a null when the column within the database does not allow a null. In those cases, the entire thing simply fails and then we have to grab the error and have someone page through thousands of lines of the input file to try to find the row which had a problem. What I really need to be able to do is configure the OLEDB Destination Adapter to redirect any rows which throw an error when they hit the database, unfortunately, you can't do this because a detsination adapater doesn't have any output (even though there is a place to configure errors with redirect being an option).

Does anyone have any ideas on how I can setup an error redirection to redirect ONLY those rows which are rejected, because the inbound file has a NULL where it shouldn't? Please don't tell me that I have to set something up to test every single column, because we are talking about over 2,000 columns which would need to be checked.