Hi everybody

 

(I hope that I'm doing this the right way.)

I'm using WebService created in .NET and I'm calling it with VFP9.

There are two methods that I'm gonna use.

One to receive data and one to send data.

The one that I'm receive data works fine but when I try to send I got some 
problem.

 

When I look at the method in VFP (in the XML Web Services in Task Pane Manager) 
it says that the syntax for it is :

(Parameter names and such have been changed.)

 

SendXML(User AS string, UserPwd AS string, service AS string, receiver AS 
string, xml AS XMLDOMNodeList, UserMessage AS string) AS VOID

 

The information I got from the company that I'm trying to send to is that the 
code for the XML should be something like this (presumably with .NET in mind) :

 

<coolio_words xmlns="http://www.company.com/schemas/inc/coolie/1"; 
message="string_1" sender="sring_2" system="strng_3">

   <customer_insert staff="string_4" ktl="string_5" reject="" batch="string_6" 
country="string_7">

      <customer cost="string_8" date="2001-01-01T00:00:00" 
costSystem="string_9" costName="string_10" />

   </customer_insert>

</coolio_words>

 

I have tried to find the solution for my problem and the closest thing I found 
is :

 

I create a form, put a button on it an in the click I drag the WebService in it 
from the toolbox.

In the code that comes automatically I put after the '* Call your XML Web 
service here.' this code here :

 

TEXT TO lcXML TEXTMERGE NOSHOW PRETEXT 7

   <coolio_words xmlns="http://www.company.com/schemas/inc/coolie/1"; 
message_id="string_1" senderId="sring_2" systemId="strng_3">

      <customer_insert staffId="string_4" ktl="string_5" rejectReason="" 
batchID="string_6" countryCode="string_7">

         <customer cost="string_8" date="2001-01-01T00:00:00" 
costSystem="string_9" costName="string_10" />

      </customer_insert>

   </coolio_words>

ENDTEXT

 

leSend = 
loWebSevice.SendXML("something_1","something_2","something_3","something_4",lcXML,"something_5")

 

When I try this I get this error :

 

Error: 1429 - OLE IDispathc exception code 0 from Client: Client:Incorrect 
number of parameters supplied for SOAP request HRESULT=0x80070057: The 
parameter is incorrect.

- Clinet:Unspecified client error. HRESULT=0x80070057: The parameter is 
incorrect.

..

Client:Incorrect number of parameters supplied for SOAP request 
HRESULT=0x80070057: The parameter is incorrect.

- Clinet:Unspecified client error. HRESULT=0x80070057: The parameter is 
incorrect.

 

What am I missing or doing wrong?

 

After searching for solution and seeing some codes I consider if my problem is :

(despite of my lack off knowledge)

- should I use '< ?xml version = "1.0" ....' and then how?

- shouldn't I use 'TEXTMERGE' to send in XML (XMLDOMNodeList). And than what is 
the best / right way to do it?

- something about schema. Is it not identified or wrongly?

- something to do with 'diffgram'. Should I use it and than how?

- is there something missing or not identified?

- is the date making the error?

 

Please help me and if you need more information please let me know, like what 
the web service and wsdl site say.

All help would be appraised.

 

I want to find a solution for this in VFP so I don't have to turn to .NET!

 

With hope that this is just a missing '( )' problem or something simple as that.

 

With thanks in advance,

Jens Reynisson



--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/aab8ac1e00010...@fylkir
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to