>>And yes, you can create a view, open it with buffering 5, append to it, and then issue a tableupdate() for all records - and then wait while Fox does the groundwork for you. It will take some time, too, but not as much as it would when sending one record at a time.
>
>Arg. I am still confused
>
>here is my scenario
>i have a local dbc which contains a table called claims
>I create a sql db called kba_sql and created a table there called tclaims (I added the t to avoid confusion in my old brain :-)
>now I want to copy the 64000+ records from vfp into sqlserver
>
>the remote view wizard asks for a data source. what do I do there? how do I create a 32 bit data source?
>isn't the Control Panel\All Control Panel Items\Administrative Tools\data source administrator 64 bit

Bitness shouldn't matter, the two sides don't really call each other's code, they communicate over whichever protocol is set. I have everything 64 bit and have no problems.

For a VFP view you should create a connection first (which I forgot, after all these years on SPT :). So fire up the wizard for the new connection, and then create the view using that connection. Mind you that this is only needed for the creation of the view - you can still open that view later with just the handle. The connection is... ahem, the weak spot here, as it is stored inside the database, and basically holds your connection string. When you deliver your app anywhere, you need a different connection there, so the connection record in the dbc must be different there, and you can't just deliver an updated dbc. Which is why nobody (AFAIK) actually uses the connection in the DBC for anything else but the initial creation of the views. After that... GenDbcX is your friend (and manual messing with the generated .prg).

What Nadya says is fine if you got no memos in your tables, then CSV is probably much faster for one time import.