>>Despite the fact that this may work with regular Visual FoxPro components, when the object is MSSoap, it doesn't work.
>
>You need to reveal these details ahead of time. What good would adding an object to a SOAP Client be?
>
>You have to keep in mind that its called SimpleOAP for a reason. YOu also have to keep in mind the cross platform capabilites of SOAP. This sort of behavior would just not work in every langauge.
>
>Try to expain what you want to accomplish, and maybe there's a better way.

We solved that situation. In order to add the required implementation to the SOAP object, we had to create a class with a pre-defined structure.