Setting Up And Testing An Error Destination

I'm sure this is pretty basic for many folks, but how do I go about setting up and testing a Data Flow element's error output?

The intent is to set up flat file that'll contain the error output from elements on the Data Flow tab of an SSIS package. Later, I'd like to have the error output go to a SQL Server table so my DBAs have access to the errors.

There is no data transformation in this package -- it's very simple, just plain, delimited text to a 2-column SQL Server table.

Here's what I've done so far:

Set up a flat file destination to capture the error output. This flat file destination points to an empty file (C:ErrorDestination.txt) on my local machine.

Grabbed the "red" output from the Data Flow element (named "Source REGIONS"). This element is a flat file source, pointing to a file named Regions.txt. I was pleased to see that the connection manager for the error output was automatically populated with the 3 columns (Flat File Source Error Output Column, Error Code, and Error Column) when I clicked on the "New" connection button in the Flat File Destination Editor.

Changed the "Error Output" for the 2 columns in the flat file source to "Redirect Row" for both the Error and Truncation columns. I understand this instructs the source to send the error-causing rows to the error destination.

I ran the package to make sure nothing has changed how it operates under normal conditions.

But, when I introduce an obvious error into the source file (removing a quote surrounding data in one row) the package blows up on the Data Flow element in the Control Flow tab, the flat file source in the Data Flow tab turns red, but nothing flows to the error destination.

I truly expected the error on the flat file source to flow into the error destination on the data flow tab.

Any ideas? I appreciate any guidance or insight you might be able to give!

Sorry for the length of this post, but I wanted to make sure I've covered my bases.

Thanks a ton!