Use Office 2003 Web Services Toolkit or VSTO with Access 2003?

  • Thread starter Thread starter sandal
  • Start date Start date
S

sandal

I will be writing an Access 2003 application using the runtime that must
pull data from a SOAP web service on the same server. I've not used the
Office 2003 Web Services Toolkit or VSTO, but I understand that both are
options for a case like this. Anyone with hands on experience want to
recommend one over the other? I have VS 2003 and VSTO.
 
Please note that this response is NOT from Microsoft: it's from a troubled
malcontent named A a r o n K e m p f

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)
 
Please note that this response is NOT from Microsoft: it's from a troubled
malcontent named A a r o n K e m p f
OK, but have any opinion re which technology would be best for my
purposes? If the prev poster was a tm named ak, is that supposed to mean
what he wrote was bogus?
 
sandal said:
OK, but have any opinion re which technology would be best for my
purposes? If the prev poster was a tm named ak, is that supposed to mean
what he wrote was bogus?

Actually, in this case his advice to use the Web Services Toolkit may
actually be the most appropriate answer. I just didn't want you thinking
that it was an official answer from Microsoft.
 
Actually, in this case his advice to use the Web Services Toolkit may
actually be the most appropriate answer. I just didn't want you thinking
that it was an official answer from Microsoft.
OK, thanks. Didn't sound much like an official answer <g>.
 
Oh, I should have asked...I mentioned in my op that I'll be distributing
my app as an Access 2003 runtime. I use the sagekey scripts. It wasn't
clear if anyone really noted the details, so would like to ask, can the
web services toolkit be rolled up into a setup routine? Or would it
require a manual installation? I imagine it can be incorporated into a
setup routine but it's a good thing to check on before I spend a bunch
of time on it.
 
Back
Top