By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,391 Members | 1,649 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,391 IT Pros & Developers. It's quick & easy.

Office XP Web Services Toolkit: Handling Complex Data Types?

P: n/a
Seems like the toolkit does not handle complex data types.

But that seems like much of the real world - once you get past something like
just looking up a SIC code or adding two numbers.

I see something about the SOAP 2.0 toolkit... then I see that there's a SOAP
3.0... and then I see a note somewhere something like "Support for SOAP 3.0 will
be discontinued on (sometime in 2005)".
Bottom line: can I deal with complex data types in a web service from MS Access?

If so, can somebody point me to a starting point?
I'm at the stage where I have the Office XP Web Services Toolkit installed and I
can feed it an http address

(e.g. "http://www.webservicex.net/WeatherForecast.asmx?WSDL")

and the toolkit automagically creates a class that invokes the service's methods
if it's just "Simple Data".
I'm guessing that I'll wind up writing my own class with am ErrorHandler, an
Initialize, and a function/sub for each of the web service's methods.

But I haven't got a clue beyond that.... It's got to be something like
concocting the XML needed to drive the methods and parsing the XMS that the
methods return, right?

--
PeteCresswell
May 2 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Per (PeteCresswell):
I'm at the stage where I have the Office XP Web Services Toolkit installed and I
can feed it an http address


Doing an end run around the Class approach - trying to pare it down to the bare
essentials, I find that code like this works for a simple data type in/out:

-------------------------------------------------
Sub xx()
Dim mySC As SoapClient
Dim myIndustryName As String

Const mySampleSicCode As String = "100"

DoCmd.Hourglass True

Set mySC = New SoapClient
mySC.mssoapinit "http://ws.invesbot.com/companysearch.asmx?WSDL"

myIndustryName = mySC.GetIndustryName(mySampleSicCode)
MsgBox myIndustryName
Set mySC = Nothing

DoCmd.Hourglass False
End Sub
-------------------------------------------------

I'm guessing that if the input/output arguments were "Complex",
that the sytax above would be the same except that:
------------------------------------------------------------
1) I'd have to create some XML into "mySampleSicCode".

2) That the string returned into myIndustryName would be XML,
from which I would somehow have to parse out the values.
-------------------------------------------------------------

If it's as simple as that and, as I've heard, XML is self-defining
would I then just have to find some sort of generic parser?
--
PeteCresswell
May 3 '06 #2

P: n/a
Per (PeteCresswell):
If it's as simple as that and, as I've heard, XML is self-defining
would I then just have to find some sort of generic parser?


Starting to look like a reference "Microsoft XML, v3.0" (Library MSXML2,
C:\WINNT\System32\msxml3.dll) is the key to all this.

True?
--
PeteCresswell
May 3 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.