>>Did you check the XML that was sent? This sounds as if my suggestion should work:
>>http://msdn.microsoft.com/en-us/library/ybce7f69(VS.80).aspx
>>Snip:
>>"When serializing objects into an XML document: If the XmlSerializer class encounters a null reference for an object corresponding to an XML element, it either generates an element that specifies xsi:nil="true" or leaves the element out entirely, depending on whether a nillable="true" setting applies."
>
>We cannot check the XML because this is under HTTPS. So, no matter what tool we would use, everything goes out encrypted.

You could use the SoapExtension class:
http://msdn.microsoft.com/en-us/library/system.web.services.protocols.soapextension.aspx
http://msdn.microsoft.com/en-us/magazine/cc164007.aspx

>Basically, when I did the test, I put loDocumentDates.stCloseDate=nothing. This has resulted in the Web Service to validate our request and reject it. There is some kind of validation out there and it cannot accept anything under 1753. So, when passing nothing, which should be the equivalent of NULL, as DBNull.Value cannot be assigned as is to a date type, this goes out of scope and cannot be validated.

This almost sounds as if they are asking that empty dates should be transmitted as null but are then refusing to accept it .......


>There is a request presently that has been sent to them in order to adjust something on their end. We will see how it goes.