Would SSIS Be The Right Tool ?

We have a web application using SQL Server 2005 to store and serve the data to forms made using .Net 2. The forms are used by customers to enter fifteen or so items if data. An important part of what the app does is to validate these 15 items of data against data brought in from the main application which is in Access 2003 (for example, did the customer enter a valid part #, did they actually purchase that part number in the qty stated, etc).

I want to periodically (nightly) schedule a copy of the lookup data from Access (2 different databases) into tables in SQL Server. The copy process would simply overwrite the existing lookup data in SQL server with the new data each night. My guess that about 250 mb of data would be copied. The two different databases are identical in structure, but different in data. They are used in two different countries.

The process as I see it would be to:

1. Delete existing lookup data.
2. Copy in data from database 1
3. Copy in data from database 2

I need to use something with enough programming power to resolve issues with primary keys, eg not copy Access table columns which contain them, and perhaps populate a column in the SQL Server lookup tables which indicate which Access database a given record came from.

If we use SSIS, then I will need to learn it, which is great as long as I am going down the right path in the first place.

Would SSIS be the right tool? Is there something more appropriate? Is there a good tutorial?

Many thanks
Mike Thomas