Thanks for your reply, Sergey, you always seem to be able to help. :)

In this case, I did as you indicated in the begining, and the source is linked to the destination, but the fields from the source are not able to be linked to the fileds in the destination. I can even preview the result set from the procedure. It seems that SS05 is unable to see the fields (field names) that come from the procedure to be able to link them to the destination fields. Without this step, you can not save that step in the package. It won't complete (unless, of course, I am doing something wrong). I have only been working with 2005 for a month or so, and am unable to find documentation on this particular implementation.

Thanks again.

Rollin

>You can drag output of the source (green line with arrow) on the Flat File destination.
>
>>I have a stored procedure that ends in a select statement, and I would like to set up a package to auto export the data to a txt file. I have been able to set up the source (the procedure) and the destination file, but am unable to map from one to the other in Integration Services Project. Nothing is listed in the source box for the
>>
>>Am I doing something wrong? Is there another (better) way to do this??
>>
>>----
>>Addition since I first wrote this (since no one has yet responded). I made a work-around by creating a permanent table, and populating the table so I can now export the data. I would prefer a cleaner solution. The export is only needed periodically, but needs to be automated. I would rather not have to delete from the table and then re-populate it, or even have it in the DB.
>>----
>>
>>All help is greatly appreciated.