I have found that the most reliable way of doing this is to write a VFP procedure to do the import. It takes a bit longer (in your case, with 100+ tables, MUCH longer), but you have TOTAL control of what goes where. And when a table structure changes, you modify your procedure to handle the change.

This is obviously not the FASTEST way to do this, but the most reliable and maintainable.

>This is a one time operation for any of our clients who are moving to SQL
>Server backend from a native VFP environment.
>The tables already exist in SQL7, but are empty.
>For these clients, the files are large (1GB+ aggregate)
>
>I've used the DTS wizard to at least create a DTS package. But then I have to go
>into each work flow diagram and select the table lock option so that the
>package does not create any transaction logs . . . there are 100+ tables.
>
>Also, over time, the structures of both databases will change.
>The structure of some of the SQL tables differ from those in VFP (mostly
>that a identity field has been added) So I would have to continually
>recreate this huge package every time there is a structure update.
>Is there a way I can create a package programmatically?
>
>What is the fastest way to do this?
>Or should I say there another way to do this?
>
>Any help would be GREATLY appreciated!
>
>Thanks in advance,
>Tim
>
>(NT4 SP6 / SQL7 SP3)