Just to throw my 2 cents in, you could also use SQL Pass-Through (SPT). It's faster than remote views, and easier to deal with than BCP. Check out the SQLCONNECT(), SQLEXEC(), and SQLDISCONNECT() functions. As Josh pointed out, you'll have to have the tables defined before hand. Also, if possible, avoid creating the SQL Server keys and/or indexes until after the data is loaded. This speeds up the process.
>There are several ways to do this. One is to create a remote view for each table and just append from your VFP tables into the remote views. If you do this, you may want to temporarily set the SQL Server database to Truncate Log on Checkpoint so that you don't overrun the transaction log.
>
>You could also use SQL Server's BCP features. This will allow you to import ASCII files into SQL Server. This would be a much faster method, but it doesn't work with memo fields.
>
>With either of these methods you would have to create the table definitions, etc. yourself or use the Upsizing wizard to create your database then move the data over using another method.
>
>>Is there any way to upsize tables to SQl Server with out using wizard . Is some there in SQl Server on in VFP. Please guide me.
>>Thanks.
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
