automation error -2146233079 80131509 Access VBA using .Net client proxy for web service

[BobAlston]

Albert or anyone else who has used Visual studio 2010 to create a client
proxy for accessing a web service, then using it from Access 2007/vba
and getting this error?

It comes when I try to set an object =new class defined in the .net module.

I recently read this but not sure how to fix

"After stripping out ALL the code, the only slightly unusual thing left
was that the exposed class inherits from a base class. Because I don't
want the base class exposed to COM it was decorated with
[ComVisible(false)]. When I finally removed this decoration from the
base class the COM class worked in VB and in scripts."
http://www.itnewsgroups.net/asp/t21245-error-80131509.aspx

Bob

[BobAlston]

I found that by using the .Net created client proxy class, the
structured parameters required were accessible by my vba without issue.
My web service requires authentication data to be placed in the SOAP
header. Accordingly a special class was defined for the soap header
structure. It is in setting an instance of this header data structure
that I get the error.

From the reading I am doing, it appears this may be because the class
which implements this header data structure inherits from other classes
which are not defined a public. So they are not visible to com and thus
the error.

Perhaps some people have used .Net created web client proxies without
any issue because they have not had to deal with authentication data in
the SOAP header.

Still looking for help from someone, somewhere who has encountered this
issue and resolved it.

bob