Hi, thanks for the replies...

>The upsize wizard isn't great, but it should handle one table with 11,000 records with no problem. Does the table have any memo or general fields with large amounts of data? That can slow things down. You may want to try manually creating the table in SQL Server. Then create a remote view in VFP and append the table to the view. Create any SQL Server indexes after you upsize the data.

I must be missing a step. After appending the table, I can browse the data in the view but it does not update the SQL Server table. Why?

>An even better option may be the SQL Server BCP utility. You'll need to export your table to ASCII first. BCP doesn't work with memo fields or generals, though.

I have tried to use BCP in several ways but keep getting the message "... Attempt to bulk-copy an oversized row to the SQL server ...". I've tried tab and comma delimited fields with no success. What am I doing wrong?

>Hi, I tried to "upsize" a VFP database container with one table (11,000) records from a Win95 PC to our WinNT server (SQL Server 6.5). It was a tad slow in creating the database/device/log but ground to almost a halt when "sending" table data. In fact it took 4 hours to get to 6%. I left it going overnight in the hope it might finish by morning. It didn't and only Ctrl+Alt+Del could rescue the PC. Can anyone help?
>>
>>Rgds
>>Petras