Dmitry,

You need to use named parameters to pass the data. Use the Parameters collection on the Command object to do this.

+++ Rick ---

>I was happy to start using the property XmlDocument.OuterXml as you suggested, when I ran into the following problem (actually I had this problem before). If you pass this property to the VFP Stored Procedure as in the following code:
>
>

>string commandText = "SP_TEST('" + oXml.OuterXml + "')";	
>

>
>the XML string is passed as a literal string and not a variable. Therefore, you hit the limit of 254 characters allowed in the literal string. But I am sure people work with XMLs larger than 254 and somehow pass them to VFP.
>
>Anybody can suggest what I might need to change?
>
>Thank you.
>
>
>>You can pass the XmlDocument to VFP, but it'll be hard to manipulate. You'd probably just want to pass the XmlDocument.OuterXml property...
>>
>>+++ Rick ---
>>
>>
>>>If you have an XML object on .NET side and you need to pass it (the XML) to the VFP (either COM object or Stored Procedure), what do you do? I don't think you can pass XML object to the VFP so you have to convert it to a variable that contains the entire XML string. What would be the syntax (in .NET) to do that?
>>>
>>>Thank you.