Hi,
I need to use SOAP from vba code in an excel book that is going to be
distributed to users. The book needs to be compatible with Win XP,2003 (and
Vista soon) and Office XP, 2003 (and 2007 if possible)
From what I have gathered, there are several options... but each of them
have major drawbacks.

1- 'Office XP Web Services Toolkit 2.0' which doesn't work with Offcie 2003
(library MSOSOAP30)
support : not sure
2- 'Office 2003 Web Services Toolkit 2.0' whcih doesn't work with Offcie 2002
(library MSOSOAP30, i.e. same name as above)
support : not sure
3- 'Soap Toolkit 3'
(library MSSOAP30, different name than above)
support: "The Microsoft SOAP Toolkit is deprecated by the .NET Framework"
retired in April 2005 - extended support March 2008

(1) & (2) are office-version specific and (3) seems to be older and soon not
supported anymore (well vba too)

For those using soap in vba, what has been your development choice? And what
would work best?

Thank you
--
Regards,
Sébastien
<http://www.ondemandanalysis.com

If you don't require a secure username and password the VBA Reference/
DOM that comes with installing MSXML 6.0 can read XML directly from a
URL.

In that case you wouldn't be using SOAP but you'd be reading XML.

You could put a username and password in the query string.

I find XML to be a viable approach when data must be fetch for the
users in real time and either:

1. I can't count on the users having an ODBC datasource for the DB
configured on their machine,

2. The distribution list is volatile

3. The users are OK with a Worksheet with VBA in it.

4. The users might use the data some day, but not want it in a
spreadsheet.

Thanks for the reply.
We have actually already implemented XML. It works well.

We are trying to implement 3 ways of getting the data in the same tool:
ADO/OLEDB, XML, and SOAP.
We have already implemented ADO/OLEDB and XML. We have tried SOAP using Web
Services Toolkit but we have to create multiple codebasis, one for each
version of Office and it is really a pain to maintain. That's why I was
wondering if there was an easier way for SOAP.

--
Regards,
Sébastien
<http://www.ondemandanalysis.com

--
Regards,
Sébastien
<http://www.ondemandanalysis.com


" wrote:

I find XML to be a viable approach when data must be fetch for the
users in real time and either:

1. I can't count on the users having an ODBC datasource for the DB
configured on their machine,

2. The distribution list is volatile

3. The users are OK with a Worksheet with VBA in it.

4. The users might use the data some day, but not want it in a
spreadsheet.