Okay, I accept that distinction... it is an SQL destination with that limitation; not an OLE-DB destination.  But, "Destinations" from that portion of the toolbox do not have success outputs, so another task after a destination isn't possible (except perhaps by either passing a result set to a new control flow, or implementing an event handler).  It is not possible within the data flow after the destination task.

Yes, an SQL Script component could have been used - which was exactly why I bought Donald Farmer's book, "Scripting SQL Server 2005 Integration Services"; but what I did appeared to work, and I still believe should have (and will) work.  The additional complexity of a script component was not justified - not only not justified; but not identified as being necessary.