What I would do is design the database in SQL Server properly, and then pump all the data in. I am sure that you will want to change and modify the design some when you use a much better relational database. Access is not much on this type of thing. You can create the same table structure in SQL, and then pump the data in, without allowing SQL Server to design the tables for you.

In the long run, it will take you much less time than trying to have some dinky app attempt to do this for you, by some automated process, and still get it incorrect. Even if you have say.... 250 tables in Access, that would take you maybe a full day to design that same database in SQL. But now you can rethink the design, solve some of the problems that Access restrictions gave you, and allow SQL Server to create the proper relationships between tables. Take my advice, you will be much further ahead by doing some work by hand.

Andrew SQLDBA