Messages
Reply
Edit
Delete02:06 pm
3P20U82NS
| From: | Frits van den Munckhof |
| To: | Rick Strahl |
Hi Fritz,
That's a VFP bug - there are certain reserved words that don't work as method and property names. For example, you can't have a property called Class in a VFP object either because the base class has that (even on SCATTER NAME objects which don'thave this property).
So there's an easy fix: Just rename the Proxy generated method in the PRG file. Make it _Cancel or Abort or something like that - anything to change the name.
+++ Rick ---
Hi Rick,
The web service I'm comsuming from VFP through your generated proxy contains a method Cancel. When calling this method in the same way as I succesfully called the other methods generated a "Methode Authoriser.Authoriser.Cancel is niet gevonden...". After checking for mistakes in the datatypes I created a breakpoint, to be able to inspect the oService object. oService DID contain "Cancel", but this was a property instead of a method (other methods showing up fine). Do you know where this property is added, since it is not standard attribute of the custom class that you use as your baseclass?
I checked if the Cancel-method was present in the proxy-prg. And it was:
************************************************************************ * Cancel ****************************************FUNCTIONCancel(CardType as String,Requestor as String,TransactionId as Int64) as CancelData
Do you have a workaround to be able to call the Cancel-method of the webservice? Or is this a naming conflict you cancel easily solve in the framework, since Cancel is a pretty obvious method-name for webservices?
TIA, Frits
BTW except for these little startup hickups, everything is working like a dream.
