Hi Alex,

You may try DTS.

>I'm at a client site with an Upsize Wizard problem. The app was designed for DBF but field conditions changed and data came several times *much* faster than it was designed for. We never expected more than a million records in several years.
>
>The program is in its 7th year, now in VFP8 SP1, and the main transactions table has 6.3 million records. Works fine but because it is a wide table, it weighs at 1.5 Gb. So I estimate that within two months it will reach the limit and die.
>
>I requested they purchase a SQL Server License. They installed SQL Server 2000 in Windows 2000 Server. All is OK. The program was easily modified to change (this table only) from DBF to SQL Server.
>
>Now I'm at the day when I want to move the data. I have not run the Upsize Wizard in years.
>I ran it today, selecting the DBC and the one table. Connection to SQL Server is fine. I created SQL DB+Log. All I need is for the wizard to create the table and upsize.
>
>The table maps fine, has simple char, num, date fields. I accept all the default coversions. The next page gets me the following error in a messagebox and can go no further:
>

"The Upsizing Wizard could not set the SQL Server 7.0 database to proper compatibility level for upsizing"

>
>I can forgive that the wizard code is old, even in VFP 8.1 and still thinks of SQL Server 7, but what does it mean with "proper compatibility level"?
>
>Any different/better ideas for upsizing 6.3 million records? (growth is now at around 25,000/day). I need to resolve this fast before we get to close to 2GB. I would like to avoid writing a slow program to SCAN..ENDSCAN and SQLExec("Insert into") that number of records.
>
>TIA