I did try the Base64binary - every time I tried it I got a similar soap error...I was trying both base64binary and byte on both the .NET and Fox sides. The only way I've gotten any success so far is to send very small character parameters. Is there a limit to binary sizes (assuming I can ever get them to work)?
I will try looking into the registry key...might be promising.
>To all:
>I am temporarily giving up on binary transfers as most of the files I need to transfer immediately are text based and I have wasted a LOT of time on it. Every time I tried, I got a "bad request" error from the SOAP engine (I think it was SOAP who was giving the error)
Yes, it seems that.
>My web service works great if I use string type in Vfoxpro, but crashes if I send a file longer than about 1K. What data type(s) can I use in VFP that will allow larger transfers of data?
1K? You must have at least 100 Kb, is the default queue size, well a bit less due to SOAP headers.
This size is defined in a registry key in the server:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSOAP\SOAPISAP
Didn't played with that. just sawn in the SOAP doc.
Have you reviewed the SOAP3 Beta? This has file attachments.
Have you tried the Base64Binary? what you get from this?
Pablo Roca - MS VFP - MVP
Clavo Congelados, S.A. (La Coruna - Spain)
Sysop of PortalFox
Steve Howie, owner
DaSH Technology
Denver, CO