>>On the Ole DB source and Ole DB Destination - Right Click, and select Edit, with the Menu you will see OLe DB Connection Manager, select your source - it will be the same for destination also.
>
>Thanks, I was able to have it working. But, I am wondering if I have to create such connection relation for each of the table I have. Basically, if I have 80 tables to migrate, do I need to do this step 80 times?
>
>Basically, all the tables are bound to the same criterias. I have a Numero field which is defined as auto incremental. When migrated to SQL Server, this should be the same as well. Right now, when I do it, it is not the case as the field is updatable from the SQL Server Management Studio interface and when I insert, it is not auto assigned.
>
>I also find that even if the package says that 326 rows have been imported. When I go in SQL Server Management Studio, I see only six rows. Everytime I do it, it says that 326 rows have been imported. But, only six new rows are showing up after each package being run.
>
>Among other things that are similar, whenever I will run the package, I need to start from scratch everytime. Basically, all tables in the SQL Server database should be emptied before importing the records from VFP.
>
>I will try to find some documentation on the topic. But, this package approach seems to be the way to go.
>
>Thanks for the help

Micheal,
Sorry for the later replies, I'm working at a client site.

SSIS does have a for loop container. You can set a counter to stop at 80 iterations.

Also, the verify your row imports, you can right click on the green flow path and then select Data Viewer / Add. This will show you the exact data that is passing through the flow. It's a pretty cool for debugging.

I hope this helps.

Carl