Data source column discovery at runtime? Help much appreciated

Hi -- I am fairly new to SSIS development, although I am starting to appreciate it more an more, especially since I have started getting into extending the object model. Here's my question:

I have a data flow that pulls data from any number of different delimited files with different numbers of columns. I have had no problem dealing with setting up run-time file locations and file names by using the expressions of a flat file data source, and i have been able to pretty easily deal with varying file delimiters by standardizing the files before they get into the data flow. however, I have not been able to come up with a solution that will allow my data source to discover its column info at run time, and then pass that information on to the data flow task. all i really care about is being able to properly parse the individual rows into individual column data by the flat file data source because the data flow itself is able to discover the actual data that the columns hold at run-time.

i would very much appreciate any feedback from anyone on possible solutions for this.

thanks!

i have seen a suggestion below from a similar problem that someone had that suggests loading all of the data as a single column and then parsing it out in the data flow. not a bad idea.

has anyone else implemented any other solutions for this?

Data Import from Multiple Tables

Hi all,
I am a newbie to .NET and would appreciate all your valublesuggestions. I have and issue were I am trying to import data from afew selected columns MS Access and a couple of columns in SQLServer Table Y and trying to populate another table X . Bothtables X and Y are in the same Database . I am wondering if I coulddesign a custom package for this task.
Ananth
There might be better ways to do this, but...
I would first create a temporary table, and take and dump all of the relevant Access data into that temporary table (via DTS). From there, joining and inserting into Table Y should be pretty easy. When you're done, delete the temporary table.
(And I say temporary, but not TEMP).
I'm sure there are more efficient ways of doing this, and of course it depends on how much data is in the access table. But probably the easiest way to create the dataset you will need for Table Y will be by using T-SQL. So having everything within the same database will make that easier.|||Thanks a lot for the suggestion. I appreciate it.