>If you are sending the files on the query string, you'll likely run into length problems quickly since most servers impose a length limit. This limit varies. The HTTP protocol does not place any a priori limit on the length of a URI, but servers can. Check to see if you are getting a 414 back, which should indicate a lengthy URI.

HTTP spec officially puts a limit of 512 bytes for the querystring. Most browsers however do not use that - IE is about 2k. Servers shouldn't care assuming buffers are not overrun (that's what Code Red has been all about).


>Likewise, if you are POSTing your XML you may encounter limits as to the maximum size of POSTed content (I often see it at 2k).

Are you saying on the server? I don't think so... IIS's first input buffer is 49k by default - POST data can be of any size per spec, so if there's an issue it's most definitely on XMLHTTP. I've sent more data than that with it, so I'm pretty sure that this works.

>Check with your website administrator to see if any limits are in effect.
>>We have tried using setrequestheader method as such:
>>loxml.setrequestheader("Content-Length",len(lcxml))
>>but this doesn't seem to change anything at all.
>>I notice that docs say that the 2nd parameter is of type bstr.
>>Could this have something to do with our failure here as we are passing a numeric value.

Binary data will truncate potentially with XMLHTTP because the text gets converted to double byte from VFP's ANSI and any NULL (CHR(0)) values in the content will cut off the string.

Finally, if XMLHTTP doesn't work raw WinInet definitely will - you can use wwIPStuff or code the raw API calls for this...

+++ Rick ---