>>>I want to export the 'dbf' file to an ascii , plain text format so that i can port the data to SQL server. Since the DATA BASE FILE is having memo field , it is exporting all fields except memo. I want memo fields also to be included as a string in my plain text file. I used the command 'COPY TO ' and was unsuccessful.
>>>
>>>then I used FWRITE and FCLOSE, FOPEN to create a text file and copied the data to text file, but it's speed is not good.
>>>
>>>I got one more problem . The Foxpro 2.6 database file is not having some entries in some rows in some fields. and when exported it sent them as NULL, but using the above method, I am not getting NULL values . So can anybody suggest a solution.
>>
>>Yup, at least, the best I can do... This is roughly based on a thread posted within that last couple of days.
>>
>>Don't use low level file handling...too slow, and too risky. (IMO)
>>
>>create a remote view of the SQL Server table you wish to copy to. (make sure it's updatable.
>>
>>Copy data from the VFP table into a table (dumpdata) with the identical structure of the view.
>>
>>SELECT the view and then APPEND FROM dumpdata.
>>
>>That should work. And prob. a lot faster than low-level files.
>>
>>Have a nice day. :)
>
>Thanx for suggestion,
>Ok. That should solve the problem, it seems if i got ODBC drivers and conectivity kit, But what happens if i use Foxpro 2.5 database , 2.6 ver and so on. every time I need to change the conectivity kit. However I will try that and inform to you. Since I am not accessing Universal Thread completely, I do not have any way to inform you, what happened about that. I often do not come to this place . Is there a way I could inform you , other than this ?

As far as older data, you can still use it within VFP without modifying it, so that shouldn't be a stumbling block.

As far as contacting me: matmbc90@ix.netcom.com is fine.