Sending that much data is bound to be slow any way you try it. It may be better to parcel out that data in some way or use a client that can report process while the data is downloading.

You might want to look at wwIPStuff and the wwHTTP class. The HTTPGetEx method can pull data and report progress so at least you can tell how much data is being sent down and how long to wait.

There's an example of this here:

http://www.west-wind.com/webconnection/wwClient_docs/index.htm?page=_0SU0QWBQI.htm

You can pull the data with CursorToXML() on the server with a VFP COM object send the string back, then simply do XMLTOCURSOR() on the other end which would be the easiest way to do this.

You can also use the SQL XML services directly - it provides an XML Web service of sorts. But it's a little more tricky to convert. You can use wwXML for that...

Regards,

+++ Rick ---





>Can anyone suggest the best approach to accessing potentially large recordset (about 30-50,000 records) over the Internet to be used to update the local VFP table? The data being pulled is in MSSQL accessible via ASP-based web page.
>
>I've tested pulling the data from ASP-page and having the page format the data to XML and sending it the client app but it seems very slow. I then tried (without success) to have MSSQL directly create the XML using the "FOR XML" clause but haven't had success directly passing this back from my ASP page.
>
>I think the best way is to create a text file and send the while file back to the client app where it can upload the data to a local cursor and finally update the local table. Any thoughs?