>Yes! I have to do many wrapping around all SOAP call. :(
>For that! .NET is better.
>
>Thanks to VFP8 and VFP9 Try Catch!

Actually that's not what I'm talking about <g>...

I did a session on Web Service best practices some time ago at DevCon that talked about the concepts of properly wrappering Web Service calls into a separate service class that can properly capture errors and provide meaningful recovery without cluttering up your application.

Unfortunately it looks like I never published the paper on my site though, so I can't point you to it. I think it ran in FoxPro Advisor at some time though.

The idea is to attach MSSOAP to a class instance and then create methods for any Web Service calls on this class on the client. I have a utility in wwSOAP that creates this class for you actually and you can download this from here:

http://www.west-wind.com/wwSOAP.asp

The proxy generator creates a base class from a Web Service that wrappers all the calls. Ideally that should then be subclassed one more time to provide a custom application level interface to the Web Service. This both isolates the Web Service code and provides consistent error handling and does roughly what ASP.NET Web References do.

+++ Rick ---


>
>>
>>You'll want to be very pro-active about Web Service errors because they will happen. Network down, DNS down, invalid response, proxy problems etc. so make sure in your code you carefully wrapper all Web Service calls into separate classes that have their own error handling so the front end application doesn't ahve to deal with this.
>>
>>+++ Rick ---