Erik,

>>I found that the XML parser consistently added about 40-45 seconds. I found this odd as we have web access here of around 3.0-3.5 MB consistently. It seemed, after some digging, that the MSFT XML parser was the culprit. When I ditched it for a straight multi-part form addpost I am now down to about 1-2 seconds for approximately the same amount of data. Perhaps in my case I added too much overhead for the amount of data...
>
>I am still not clear on whether you are complaining about response times or parsing times.

It appears to me that it is in the parsing.

>
>It sounds like you are talking about extremely large datasets if you are talking 40 seconds to parse... with datasets this large XML might no be the best vehicle, because its extremely bloaty.

Right. What do you consider as a 'large dataset'? I was testing 100 records of about 10 fields if I correctly recall.

>
>As far as response times go, my server side framework typically deals with the average request for a single record RS in about .05 seconds. I have stress tested the application using 3 WC instances to about 75000 hits per hour with no apparent leaks. This is with the business objects running in COM+... if they were compiled into the WC app, I am sure I would see even better performance.

Interesting. In my case I may have as few as one record (about 12 fields) to 1000.

>
>>Yeah.. I'd think that we VFP'ers should get up to speed with ADO.
>
>As far as accessing SQL Server and running stored procedures, its an extremely graceful way to go.

Righto. I'm going to be looking in this direction.